Re: pylint style convention

2007-07-23 Thread Ben Finney
[EMAIL PROTECTED] (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.OptionParser(usage='

Re: pylint style convention

2007-07-23 Thread 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

Re: pylint style convention

2007-07-23 Thread Matt McCredie
Which style convention is it referring to? Should these really be all caps? I think pylint is expecting that any variables declared outside of a function should be constants with special meanings (similar to #define or enum values in c). So, I guess to get rid of that message you should do som

pylint style convention

2007-07-23 Thread 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.OptionParser(usage='usage: %prog [OPTIONS]') pa