[Python-apps-team] Bug#647833: Should support ConfigParser style files

Guido Günther agx at sigxcpu.org
Sun Nov 6 18:01:30 UTC 2011


Package: pychecker
Version: 0.8.19-3
Severity: wishlist

Hi,
it's quiet common these days to configure tools needed to build a python
module via a configuration file parseable via ConfigParser (and usually
called setup.cfg). 

I'd be great if pychecker would support this as well. So while it's
possible to have a config file like:

packageImportUsed = 1
reimportSelf = 1

it's not currently possible to have one like:

[pychecker]
packageImportUsed = 1
reimportSelf = 1

[epydoc]
epyoption1 = 1
epyoption2 = 2

[nosetests]
noseoption1 = bar
noseoption2 = foo


Since pychcker doesn't know about sections and therefore doesn't ignore
unknown sections.
Cheers,
 -- Guido


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pychecker depends on:
ii  python     2.7.2-9
ii  python2.6  2.6.7-3
ii  python2.7  2.7.2-5

pychecker recommends no packages.

pychecker suggests no packages.

-- no debconf information





More information about the Python-apps-team mailing list