Under certain circumstances cgitb.scanvars fails with
because of an unititialized value variable. This bug is
present in 2.3.3 and 2.4a0.

The following script demonstrates
#####start
import cgitb;cgitb.enable()

def err(L):
    if 'never' in L:
        return
    if 1: print \
    '\n'.join(L)
    v=2

err(['',None])
#####finish

when run this results in mangled output because scanvars
attempts to evaluate '\n'.join(L) where L=['',None]. A
fix is to set value=__UNDEF__ at the start of scanvars.

Index: cgitb.py
===================================================================
RCS file: /cvsroot/python/python/dist/src/Lib/cgitb.py,v
retrieving revision 1.11
diff -r1.11 cgitb.py
63c63
<     vars, lasttoken, parent, prefix = [], None, None, ''
---
>     vars, lasttoken, parent, prefix, value = [],
None, None, '', __UNDEF__

Logged In: YES 
user_id=6946

The script cgitb_scanvars_bug.py produces mangled output
under 2.3.3 and 2.4a0. The error is caused by an error
during evaluation in cgitb.scanvars. I believe a fix is to
intialize value to __UNDEF__.

Patch python-2.4a0-966992.patch appears to fix in 2.3.3 and
2.4a0. There may be other ways in which scanvars can error,
but I haven't found them yet :(

Logged In: YES 
user_id=11375

Applied; thanks!