[issue39860] configparser - no support for cascading defaults (as defined by MySQL)

2022-02-09 Thread Ben Griffin
Ben Griffin added the comment: This is still being ignored. It's a bug, because it prevents the ini file from being used by other clients. -- versions: +Python 3.10, Python 3.11, Python 3.8, Python 3.9 ___ Python tracker

[issue39860] configparser - no support for cascading defaults (as defined by MySQL)

2020-03-05 Thread Ben Griffin
Ben Griffin added the comment: Having looked at the code, I believe that it is best NOT to interfere with the 'default_section' value of the class, as it is used as a proxy to _defaults, whereas the section parameter of get() is easily extended. The actual changes are all to the method

[issue39860] configparser - no support for cascading defaults (as defined by MySQL)

2020-03-05 Thread Roundup Robot
Change by Roundup Robot : -- keywords: +patch nosy: +python-dev nosy_count: 1.0 -> 2.0 pull_requests: +18148 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18791 ___ Python tracker

[issue39860] configparser - no support for cascading defaults (as defined by MySQL)

2020-03-05 Thread Ben Griffin
New submission from Ben Griffin : While there is now support for a single default group, mysql documentation is clear that there is a cascade of groups for option settings, normally starting with [client], and including version numbers.. This allows generic settings to be overridden by