Stig Johan Berggren added the comment:
That's fair, I didn't consider consistency with dicts' `get`. Maybe a
ConfigParser object could have an option to raise errors, because they are
useful for discovering errors in config files.
I still find the remark about the parser-le
Change by Stig Johan Berggren :
--
keywords: +patch
pull_requests: +8009
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34242>
___
_
New submission from Stig Johan Berggren :
`get()` on a ConfigParser object behaves differently from `get()` on a section.
The former raises an exception when the key does not exist and no fallback has
been explicitly set. The latter returns None, with no option to raise an error
for missing
Change by Stig Johan Berggren :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue34083>
___
___
Python-bugs-list mailing list
Unsub
Change by Stig Johan Berggren :
--
keywords: +patch
pull_requests: +7768
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34083>
___
_
Stig Johan Berggren added the comment:
I'll try to patch it myself.
--
___
Python tracker
<https://bugs.python.org/issue34083>
___
___
Python-bugs-list m
New submission from Stig Johan Berggren :
The section about iterators in the Functional Programming HOWTO
(https://docs.python.org/3/howto/functional.html#data-types-that-support-iterators)
states the following about looping over dictionary keys:
"Note that the order is essentially r
