On Sun, Aug 1, 2010 at 12:27 PM, News123 wrote:
> Hi,
>
>
> On 07/31/2010 11:04 AM, Matteo Landi wrote:
>> What are the messages one should really care about while evaluating
>> its code using pylint? It's easy to get 5 scored with a "lot of public
>> methods" or bad named variables such as 'x' or
Hi,
On 07/31/2010 11:04 AM, Matteo Landi wrote:
> What are the messages one should really care about while evaluating
> its code using pylint? It's easy to get 5 scored with a "lot of public
> methods" or bad named variables such as 'x' or 'y' .. Have you got any
> config file to share?
The mos
What are the messages one should really care about while evaluating
its code using pylint? It's easy to get 5 scored with a "lot of public
methods" or bad named variables such as 'x' or 'y' .. Have you got any
config file to share?
On Sat, Jul 31, 2010 at 2:48 AM, Dan Stromberg wrote:
>
> On Fri,
On Fri, Jul 30, 2010 at 12:18 PM, News123 wrote:
> On 07/30/2010 03:12 PM, wheres pythonmonks wrote:
> > I am starting to use pylint to look at my code and I see that it gives a
> rating.
> > What values do experienced python programmers get on code not
> > targeting the benchmark?
> >
> > I wrot
On 07/30/2010 03:12 PM, wheres pythonmonks wrote:
> I am starting to use pylint to look at my code and I see that it gives a
> rating.
> What values do experienced python programmers get on code not
> targeting the benchmark?
>
> I wrote some code, tried to keep it under 80 characters per line,
>
wheres pythonmonks wrote:
> I am starting to use pylint to look at my code and I see that it gives a
> rating. What values do experienced python programmers get on code not
> targeting the benchmark?
>
> I wrote some code, tried to keep it under 80 characters per line,
> reasonable variable names
