➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: add SafeConfigParser to __all__
Type: Stage:
Components: Library (Lib) Versions: Python 2.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: quiver, rhettinger
Priority: normal Keywords: patch

Created on 2003-08-18 09:59 by quiver, last changed 2022-04-10 16:10 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
ConfigParser.py.diff quiver, 2003-08-18 09:59
Messages (2)
msg44466 - (view) Author: George Yoshida (quiver) (Python committer) Date: 2003-08-18 09:59 
Starting with Python 2.3, SafeConfigParser is preferred 
over ConfigParser.
http://www.python.org/doc/current/lib/module-
ConfigParser.html#l2h-1231
So why not add SafeConfigParser to __all__?

There's another fix.
RawConfigParser._read has a strange code.

  # allow empty values
  if optval == '""':
      optval = ''

This if-condition is evaluated true if and only if 
name=value pair is as follows:
  name = ""
and this code converts the value to an empty string, ''.

'""' is a string of two double quotes and '' is an empty 
string.
They're totally different.

I think this part is redundant.
msg44467 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2003-09-01 23:29 
Logged In: YES 
user_id=80475

The double quoting part seems fine to me.  If it is driving 
you nuts, re-open this patch and assign to Barry Warsaw who 
wrote those lines.

The part about SafeConfigParser is reasonable.  Am updating 
the files now.
History
Date User Action Args
2022-04-10 16:10:41adminsetgithub: 39082
2003-08-18 09:59:15quivercreate