Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read

Liste des GroupesRevenir à cl python 
Sujet : Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read
De : jon+usenet (at) *nospam* unequivocal.eu (Jon Ribbens)
Groupes : comp.lang.python
Date : 29. Oct 2024, 16:33:57
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <slrnvi2035.372.jon+usenet@raven.unequivocal.eu>
References : 1
User-Agent : slrn/1.0.3 (Linux)
On 2024-10-29, Loris Bennett <loris.bennett@fu-berlin.de> wrote:
Hi,
>
With Python 3.9.18, if I do
>
    try:
        with open(args.config_file, 'r') as config_file:
            config = configparser.ConfigParser()
            config.read(config_file)
            print(config.sections())
>
i.e try to read the configuration with the variable defined via 'with
... as', I get
>
   []
>
whereas if I use the file name directly
>
    try:
        with open(args.config_file, 'r') as config_file:
            config = configparser.ConfigParser()
            config.read(args.config_file)
            print(config.sections())
I get
>
  ['loggers', 'handlers', 'formatters', 'logger_root', 'handler_fileHandler', 'handler_consoleHandler', 'formatter_defaultFormatter']
>
which is what I expect.
>
If I print type of 'config_file' I get
>
 <class '_io.TextIOWrapper'>
>
whereas 'args.config_file' is just
>
 <class 'str'>
>
Should I be able to use the '_io.TextIOWrapper' object variable here?  If so how?
>
Here
>
  https://docs.python.org/3.9/library/configparser.html
>
there are examples which use the 'with open ... as' variable for writing
a configuration file, but not for reading one.

As per the docs you link to, the read() method only takes filename(s)
as arguments, if you have an already-open file you want to read then
you should use the read_file() method instead.

Date Sujet#  Auteur
29 Oct 24 * Using 'with open(...) as ...' together with configparser.ConfigParser.read12Loris Bennett
29 Oct 24 +* Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read9Jon Ribbens
30 Oct 24 i`* Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read8Loris Bennett
30 Oct 24 i `* Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read7Jon Ribbens
30 Oct 24 i  `* Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read6Loris Bennett
30 Oct 24 i   `* Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read5Jon Ribbens
31 Oct 24 i    `* Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read4Loris Bennett
31 Oct 24 i     +- Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read1Jon Ribbens
31 Oct 24 i     +- Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read1Karsten Hilbert
31 Oct 24 i     `- Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read1MRAB
29 Oct 24 +- Re: Using 'with open(...) as ...' together with configparser.ConfigParser.read1MRAB
30 Oct 24 `- Re: Using 'with open(...) as ...' (Posting On Python-List Prohibited)1Lawrence D'Oliveiro

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal