[issue35448] ConfigParser .read() - handling of nonexistent files

Terry J. Reedy added the comment: FWIW, I agree with closing this. I already changed my mind from my earlier comment and decided that IDLE should maybe switch to using open and read_file in different places, for the reasons given above. It might make testing without depending on a local

[issue35448] ConfigParser .read() - handling of nonexistent files

Serhiy Storchaka added the comment: > There is a use case of this (which some of tools depends) about checking if > configuration exists and if not, raising an error. Now, they can solve this > by just adding check_exist argument. No, it can be solved by using open() and read_file(). It can

[issue35448] ConfigParser .read() - handling of nonexistent files

STINNER Victor added the comment: > I would expect that this basic usage is very popular. If the file doesn't > exist, the normal usage pattern fails in a confusing way: (...) Well, the configparser is well defined. As you wrote: "If a file named in filenames cannot be opened, that file

[issue35448] ConfigParser .read() - handling of nonexistent files

Batuhan added the comment: > I do not think that adding an extra parameter to .read() will solve any > problem. There is a use case of this (which some of tools depends) about checking if configuration exists and if not, raising an error. Now, they can solve this by just adding check_exist

[issue35448] ConfigParser .read() - handling of nonexistent files

Serhiy Storchaka added the comment: I do not think that adding an extra parameter to .read() will solve any problem. You need to read the documentation of read() to use this feature. You need to change your code, and this will work only in new version of Python, so you will need to support

[issue35448] ConfigParser .read() - handling of nonexistent files

Change by Batuhan : -- versions: +Python 3.9 -Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35448] ConfigParser .read() - handling of nonexistent files

Change by Batuhan : -- keywords: +patch pull_requests: +16452 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/16920 ___ Python tracker

[issue35448] ConfigParser .read() - handling of nonexistent files

Adrian Wielgosik added the comment: Yeah, I lost steam on this issue, sorry. Go ahead :) -- ___ Python tracker ___ ___

[issue35448] ConfigParser .read() - handling of nonexistent files

Batuhan added the comment: Adrian are you still want to work on this or can i take it? -- nosy: +BTaskaya ___ Python tracker ___

[issue35448] ConfigParser .read() - handling of nonexistent files

Terry J. Reedy added the comment: Since the code and doc agree, and since the proposal is to add a call parameter, this would be an enhancement for next release only, not a bug fix. The proposal seems reasonable. I might use it for IDLE. IDLE uses .read within this subclass method.

[issue35448] ConfigParser .read() - handling of nonexistent files

Change by hongweipeng : -- nosy: +hongweipeng ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35448] ConfigParser .read() - handling of nonexistent files

Change by David Heiberg : -- nosy: +dheiberg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35448] ConfigParser .read() - handling of nonexistent files

Change by Karthikeyan Singaravelan : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35448] ConfigParser .read() - handling of nonexistent files

New submission from Adrian Wielgosik : Documentation of ConfigParser says: > If a file named in filenames cannot be opened, that file will be ignored. > This is designed so that you can specify an iterable of potential > configuration file locations (for example, the current directory, the