pylint style convention

[Mick Charles Beaver]

Hello,

I've been looking into using PyLint on some of my programs, just as a
best practices kind of thing.

Here's a snippet:
#============== =============== =============== =============== ===========
if __name__ == '__main__':
parser = optparse.Option Parser(usage='u sage: %prog [OPTIONS]')
parser.add_opti on('-c', '--config',
action='store',
type='string',
dest='configFil ename',
help='config file containing defaults')
(options, args) = parser.parse_ar gs()
#============== =============== =============== =============== ===========

Now, PyLint reports the following convention warnings:
C:158: Invalid name "parser" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)
C:170: Invalid name "options" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)
C:170: Invalid name "args" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)

Which style convention is it referring to? Should these really be all
caps?

Thank you,
Mick

[Michael Hoffman]

Mick Charles Beaver wrote:

Hello,

I've been looking into using PyLint on some of my programs, just as a
best practices kind of thing.

Here's a snippet:
#============== =============== =============== =============== ===========
if __name__ == '__main__':
parser = optparse.Option Parser(usage='u sage: %prog [OPTIONS]')
parser.add_opti on('-c', '--config',
action='store',
type='string',
dest='configFil ename',
help='config file containing defaults')
(options, args) = parser.parse_ar gs()
#============== =============== =============== =============== ===========

Now, PyLint reports the following convention warnings:
C:158: Invalid name "parser" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)
C:170: Invalid name "options" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)
C:170: Invalid name "args" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)

Which style convention is it referring to? Should these really be all
caps?

There's a style convention that global constants at file scope are
defined in all caps.

Personally, I do all my optparsing in a special function rather than in
the __name__ == '__main__' block.
--
Michael Hoffman

[Ben Finney]

mi**@cs.wisc.ed u (Mick Charles Beaver) writes:

Here's a snippet:

pylint is reporting line numbers. Can you show us line numbers for
this snippet?

#============== =============== =============== =============== ===========
if __name__ == '__main__':
parser = optparse.Option Parser(usage='u sage: %prog [OPTIONS]')
parser.add_opti on('-c', '--config',
action='store',
type='string',
dest='configFil ename',
help='config file containing defaults')
(options, args) = parser.parse_ar gs()
#============== =============== =============== =============== ===========

Now, PyLint reports the following convention warnings:
C:158: Invalid name "parser" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)
C:170: Invalid name "options" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)
C:170: Invalid name "args" (should match (([A-Z_][A-Z1-9_]*)|(__.*__))$)

These warnings are for line 158 and line 170, which covers a range of
13 lines. Your code snippet is only 8 lines long. So at least one of
those two lines that have warnings reported are not in the code you've
shown to us.

--
\ "Too many Indians spoil the golden egg." -- Sir Joh |
`\ Bjelke-Petersen |
_o__) |
Ben Finney