Title: ConfigParser and nonexistent file
Type: Stage:
Components: Documentation Versions:
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: fdrake Nosy List: fdrake, mdcowles
Priority: normal Keywords:

Created on 2001-12-07 21:04 by mdcowles, last changed 2001-12-07 21:39 by fdrake. This issue is now closed.

Messages (2)
msg8061 - (view) Author: Matthew Cowles (mdcowles) Date: 2001-12-07 21:04
If you give ConfigParser's read() method the name of a
file that doesn't exist, you get back an empty

That may be reasonable but since other modules from the
standard library generally don't work that way (dbm,
netrc), it may be worth emphasizing in the
documentation that that's what happens.
msg8062 - (view) Author: Fred Drake (fdrake) (Python committer) Date: 2001-12-07 21:39
Logged In: YES 

No, that's not reasonable at all, but we can't change it
this late in the game.  ;-(

I've added an explanation of this and how it can be used
effectively in Doc/lib/libcfgparser.tex revisions 1.21 and
Date User Action Args
2001-12-07 21:04:47mdcowlescreate