http://mail.python.org/pipermail/python-checkins/2003-April/035592.html

so that Python 2.1-maint can be built on RedHat 9

and Zope 2.6 (which requires Python 2.1.x) isn't dead yet.

Duh.  The do_EOF() implementation was bogus.  Make it more like
do_quit() -- but print a blank line first.

like releasing 2.1.4 tomorrow. :-)

urlparse.py.  These were new features in 2.2, and shouldn't be added
to 2.1 this late in the game.  There was one use of urlsplit() in
httplib.py (the urlparse.py change was done as part of a backport of a
bugfix to httplib.py); this use is replaced with a call to urlparse()
without changing the effect (only the returned netloc is used).

Address SF bug #577530: del __builtins__ breaks out of rexec

Using the suggestion there: add_module() forces __builtin__ back; this
fixes r_exec, r_eval, r_execfile.

This does not mean that rexec is now considered safe!  But for those
willing to take the risk, it's safer than before.  (Note that a safety
analysis of the code module would be wise if you plan to use the
interactive console for real -- I've only ever used it to play with
restricted mode.)

Fix for SF bug 601077 by Zack Weinberg.

The new execvpe code would sometimes do the wrong thing when a
non-executable file existed earlier in the path and an executable file
of the same name existed later in the path.  This patch restores the
proper behavior (which is to execute the second file).  When only a
non-executable file exists, the correct error is still reported.

Some IPv6-specific changes crept into the 2.1 branch when I backported
other bug fixes.

since a documentation patch included \ulink.  Adding this here makes
back-porting further documentation patches easier than having to remove
\ulink from the patches.
Closes SF bug #598996.

Closes SF patch #600861.

the extension building phase.

1) Do not attempt to exec a file which does not exist
just to find out what error the operating system
returns. This is an exploitable race on all platforms
that support symbolic links.

2) Immediately re-raise the exception if we get an
error other than errno.ENOENT or errno.ENOTDIR. This
may need to be adapted for other platforms.

Change _begin() back to begin().
Fix for SF bug 579107.
Fix for SF bug #432621: httplib: multiple Set-Cookie headers
Fix SF bug #575360
Handle HTTP/0.9 responses.

The 2.1 maintenance branch is now identical to the trunk through rev
1.54 of httplib.py.

Fix typo.

(which makes it more clear).
Closes SF bug #571767.

hints about how to work around it.
Closes SF bug #530637.

when used as part of the import statement.

Note that both "as" and "None" becoming keywords in the future.

Closes SF bug #553262.

Closes SF bug #551912.

# On a Linux with large file support (LFS) using a Python without LFS,
# stat() will raise EOVERFLOW.  This unambiguously indicates that the
# file exists because it only occurs when the size of the file can't
# find into the stat struct.

This change is only needed for Python 2.1, because LFS is
automatically configured starting with Python 2.2.

Based on patch contributed by Sean Reifschneider.
Closes SF patch #570618.

This closes SF patch #569832.

Closes SF bug #523473.

Closes SF bug #568577.

constributed by David Abrahams.
This closes SF patch #568081.

Closes SF patch #567867.

Added a couple of minor clarifications present in the 2.2.x and 2.3
version of the documentation which also apply to 2.1.x.

the semantics and presentation used in the library reference.
Added an explanation of the use of [...] to denote optional arguments, since
this is the only use of this in a signature line.
Closes SF bug #567127.

if co_stacksize was > 32767 (the maximum value
which can be stored in 16 bits (signed)),
the PyCodeObject would be written wrong.
So on the second import (reading the .pyc)
would cause a crash.

Since we can't change the PYC magic, we
go on (silently), but don't write the file.
This means everything will work, but
a .pyc will not be written and the file will need
to be parsed on each import.

SF bug 533625 (Armin Rigo). rexec: potential security hole

If a rexec instance allows writing in the current directory (a common
thing to do), there's a way to execute bogus bytecode.  Fix this by
not allowing imports from .pyc files (in a way that allows a site to
configure things so that .pyc files *are* allowed, if writing is not
allowed).

fixed an old buglet that caused bdb to be unable to
continue in the botframe, after a breakpoint was set.
the key idea is not to set botframe to the bottom level frame,
but its f_back, which actually might be None.
Additional changes: migrated old exception trick to use
sys._getframe(), which exists both in 2.1 and 2.2 .

Note: I believe Mark Hammond needs to look over his code now.
F5 correctly starts up in the debugger, but later on doesn't stop at a given
breakpoint any longer.

kind regards - chris