[Python-Dev] How about updating OrderedDict in csv and configparser to regular dict?
INADA Naoki
songofacandy at gmail.com
Thu Jan 31 03:00:49 EST 2019
More information about the Python-Dev mailing list
Thu Jan 31 03:00:49 EST 2019
- Previous message (by thread): [Python-Dev] How about updating OrderedDict in csv and configparser to regular dict?
- Next message (by thread): [Python-Dev] How about updating OrderedDict in csv and configparser to regular dict?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm sorry, configparser is changed already. https://bugs.python.org/issue33504 On Thu, Jan 31, 2019 at 4:52 PM INADA Naoki <songofacandy at gmail.com> wrote: > > Hi, > > csv.DictReader uses OrderedDict by default, from Python 3.6. > But it doesn't make sense anymore, like namedtuple._asdict(). > How about changing default dict type back to regular dict. > > Python is widely used for handling learge data. So I think > changing default dict type to OrderedDict was performance > and memory usage regression in 3.6. > > Additionally, configparser uses OrderedDict by default from Python 3.6 too. > > I am not sure about `parser['section1'] == parser['section2']` is not used yet. > But we broke it once in 3.6 by changing dict to OrderedDict. Are there any > issue report caused by this backward incompatibility? > > And I think performance and memory efficiency is not so important for > configparser, unlike csv. > > I'm > > * +1 about changing csv.DictReader's default dict type > * +0.5 about changing configparser's default dict type. > > How do you think? > > Regards, > -- > INADA Naoki <songofacandy at gmail.com> -- INADA Naoki <songofacandy at gmail.com>
- Previous message (by thread): [Python-Dev] How about updating OrderedDict in csv and configparser to regular dict?
- Next message (by thread): [Python-Dev] How about updating OrderedDict in csv and configparser to regular dict?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list