[Python-Dev] Bug tracker reviews

[Tony Meyer]

As promised, here are five bug reviews with recommendations.  If they help 

[ 1112812 ] Patch for Lib/bsddb/__init__.py to work with modulefinder
<http://sourceforge.net/tracker/index.php?func=detail&aid=1112812&group_id=5
470&atid=305470>

get reviewed, then that'd be great.  Otherwise I'll just take the good karma
and run :)

-----

[ 531205 ] Bugs in rfc822.parseaddr()
<http://sourceforge.net/tracker/index.php?func=detail&aid=531205&group_id=54
70&atid=105470>

What to do when an email address contains spaces, when RFC2822 says it
can't.  At the moment the spaces are stripped.  Recommend closing "Won't
Fix", for reasons outlined in the tracker by Tim Roberts.

[ 768419 ] Subtle bug in os.path.realpath on Cygwin
<http://sourceforge.net/tracker/index.php?func=detail&aid=768419&group_id=54
70&atid=105470>

Agree with Sjoerd that this is a Cygwin bug rather than a Python one (and no
response from OP for a very long time).  Recommend closing "Won't Fix".

[ 803413 ] uu.decode prints to stderr
<http://sourceforge.net/tracker/index.php?func=detail&aid=803413&group_id=54
70&atid=105470>

The question is whether it is ok for library modules to print to stderr if a
recoverable error occurs.  Looking at other modules, it seems uncommon, but
ok, so recommend closing "Won't fix", but making the suggested documentation
change.
(Alternatively, change from printing to stderr to using warnings.warn, which
would be a simple change and possibly more correct, although giving the same
result).

[ 989333 ] Empty curses module is loaded in win32
<http://sourceforge.net/tracker/index.php?func=detail&aid=989333&group_id=54
70&atid=105470>

Importing curses loads an empty module instead of raising ImportError on
win32.  I cannot duplicate this: recommend closing as "Invalid".

[ 1090076 ] Defaults in ConfigParser.get overrides section values
<http://sourceforge.net/tracker/index.php?func=detail&aid=1090076&group_id=5
470&atid=105470>

Behaviour of ConfigParser doesn't match the documentation.  The included
patch for ConfigParser does fix the problem, but might break existing code.
A decision needs to be made which is the desired behaviour, and the tracker
can be closed either "Won't Fix" or "Fixed" (and the fix applied for 2.5 and
2.4.1).

=Tony.Meyer