[Python-bugs-list] [ python-Bugs-448025 ] Fix for #404535 not in Python 2.0x
noreply@sourceforge.net
noreply@sourceforge.net
Sun, 05 Aug 2001 11:55:39 -0700
Bugs item #448025, was opened at 2001-08-04 16:05
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=448025&group_id=5470
Category: Extension Modules
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: eXom (jkuan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix for #404535 not in Python 2.0x
Initial Comment:
The fix is not in Python 2.0 or Python 2.0.1. However,
according to the fix date, this fix is quite before the
release of Python 2.0.
I personally think this fix is needed to put in 2.0 or
later because the ConfigParser.remove_option is purely
not working and raise exception.
----------------------------------------------------------------------
>Comment By: Martin v. Löwis (loewis)
Date: 2001-08-05 11:55
Message:
Logged In: YES
user_id=21627
#404535 was closed not because it was fixed, but because
it is a duplicate of #404536.
The bug reported for remove_option was fixed in revision
1.24 of ConfigParser.py, which was a response to bug
report #124324.
Both Python 2.0 and 2.0.1 have shipped with version 1.23
of ConfigParser.py. Since they are already released, the
contents of these releases cannot be changed anymore.
Both Python 2.1 and 2.1.1 do include the fix, as they
include revisions 1.32 and 1.32.4.1 of that file,
respectively, so the bug is fixed in "2.0 or later". I
believe it is highly unlikely that a release 2.0.2 of
Python will be made.
If you are not satisfied with this response, please
explain in more detail what it is that you are requesting.
Otherwise, I suggest to close this report as "Works for
me".
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=448025&group_id=5470