[issue9421] configparser.ConfigParser's getint, getboolean and getfloat don't accept `vars`

Fred L. Drake, Jr. report at bugs.python.org
Sat Sep 4 06:37:31 CEST 2010


Fred L. Drake, Jr. <fdrake at acm.org> added the comment:

The patch has been commited largely as-is (r84486).

I'm not happy with the documentation yet:

- Markup like this:

    .. method:: ConfigParser.getint(section, option, raw=False,
                [vars, default])

  doesn't sit well with me.  I'm going to dig around current practice
  a bit and discuss with Georg sometime over the next few days, and
  see how best to adjust that.

- Inclusion of references to internal names in the API docs, like this
  in the signatures:

    comment_prefixes=_COMPATIBLE

  is just bad form.  Again, we need a better way.  I suspect there is
  little if any considered precedent, so we'll come up with something.

Neither of these are blockers; we can adjust this independently of the
code and doocumentation content.  (It's not part of the feature.)

Leaving this issue open for the completion of these changes.

----------
resolution:  -> accepted

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9421>
_______________________________________


More information about the Python-bugs-list mailing list