[issue18159] ConfigParser getters not available on SectionProxy

Roundup Robot added the comment: New changeset 2c46a4ded259 by Łukasz Langa in branch 'default': Closes #18159: ConfigParser getters not available on SectionProxy https://hg.python.org/cpython/rev/2c46a4ded259 New changeset 5eb95d41ee43 by Łukasz Langa in branch 'default': Closes #18159: ConfigP

[issue18159] ConfigParser getters not available on SectionProxy

Łukasz Langa added the comment: The new implementation also automatically covers get*() methods added on subclasses, no need to use converters= in that case. -- ___ Python tracker _

[issue18159] ConfigParser getters not available on SectionProxy

Łukasz Langa added the comment: The reason I didn't commit that patch before was that I wasn't sure whether making this change wouldn't create any unexpected backwards incompatibility. In fact, if I committed the patch as is, it would. I solved this by leaving getint, getfloat and getboolean

[issue18159] ConfigParser getters not available on SectionProxy

Changes by Łukasz Langa : -- versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue18159] ConfigParser getters not available on SectionProxy

João Bernardo added the comment: ping? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue18159] ConfigParser getters not available on SectionProxy

João Bernardo added the comment: Was the patch accepted yet? Looks good to me -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue18159] ConfigParser getters not available on SectionProxy

Łukasz Langa added the comment: There are several reasons why `get*()` methods are redefined on the section proxy. First of all, explicit is better than implicit. Secondly, the order of arguments is different: `parser.get()` has the fallback argument as the last (and keyword-only), whereas `pa

[issue18159] ConfigParser getters not available on SectionProxy

João Bernardo added the comment: > Overriding __getattr__ doesn't look like the best solution Another idea would be to allow the proxy class to be selectable, but this would require the user to do much more coding for this simple thing... I believe a proxy should be dynamic enough to avoid hav

[issue18159] ConfigParser getters not available on SectionProxy

Łukasz Langa added the comment: This is a reasonable feature request. Overriding __getattr__ doesn't look like the best solution, though. Let me think this over. -- assignee: -> lukasz.langa ___ Python tracker __

[issue18159] ConfigParser getters not available on SectionProxy

Changes by R. David Murray : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue18159] ConfigParser getters not available on SectionProxy

New submission from João Bernardo: The configparser.RawConfigParser class implements some `get` methods: get, getint, getfloat, getboolean but if any of these get overridden on a subclass(with other arguments) or new ones are added (e.g. getlist), there's no way a SectionProxy instance wil