[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-list
Subject:    Re: Why no warnings when re-assigning builtin names?
From:       Seebs <usenet-nospam () seebs ! net>
Date:       2011-08-31 21:57:06
Message-ID: slrnj5tbhc.sup.usenet-nospam () guild ! seebs ! net
[Download RAW message or body]

On 2011-08-31, Chris Torek <nospam@torek.net> wrote:
> (I realize this thread is old.  I have been away for a few weeks.
> I read through the whole thread, though, and did not see anyone
> bring up this one particular point: there is already a linting
> script that handles this.)

Yes.  I've found pylint... A weird mix of "very helpful, thanks" and
"oh, come off it".  A thread about pylint is where I got my example of
the natural Python way to express a parabola:
	theValueRepresentingTheYAxisLocationOfThePoint = 
		theValueRepresentingTheXAxisLocationOfThe Point *
		theValueRepresentingTheXAxisLocationOfThe Point

I still say that there are times when short names are natural and
idiomatic, and much clearer than long names.  :P

But I do think that, given the basic assumption that pylint is a core
tool for vetting code, it is probably adequate for it to provide the
warnings.

-s
-- 
Copyright 2011, all wrongs reversed.  Peter Seebach / usenet-nospam@seebs.net
http://www.seebs.net/log/ <-- lawsuits, religion, and funny pictures
http://en.wikipedia.org/wiki/Fair_Game_(Scientology) <-- get educated!
I am not speaking for my employer, although they do rent some of my opinions.
-- 
http://mail.python.org/mailman/listinfo/python-list
[prev in list] [next in list] [prev in thread] [next in thread]