The attached 3-file shar archive demonstrates a problem I saw in a larger program.
In short, when I use optparse (I usually do argument parsing by hand, so hadn't noticed until working on someone else's code) in combination with pylint, pylint doesn't appear to see what attributes should exist in the "options" return from optparse, and what attributes should not. Pylint gives this code a 10/10 on my system, even though it's referencing a nonexistent attribute. Is there something I can do to give pylint better visibility into what's happening, short of rewriting with manual option parsing? Perhaps pylint knows about some other option parsing module? Or are the usual argument parsers just too dynamic? Thanks! -- Dan Stromberg
pylint_optparse.shar
Description: Unix shell archive
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
