On 2/27/07, hg <[EMAIL PROTECTED]> wrote:
Michele Simionato wrote:
> pychecker
Thanks all ... pydev extension does not however ... will have to install
pychecker also.
Just as a note: pydev extensions 1.2.8 supports that... (just released)
Cheers,
Fabio
--
http://mail.python.org/mailman/
hg <[EMAIL PROTECTED]> writes:
> I spent a few hours find this bug:
>
> value == self.Get_Value()
> if value == WHATEVER:
>do this
>
> instead of
> value = self.Get_Value()
> if value == WHATEVER:
>do this
>
> Is there a way to avoid such a bug with some type of construct ?
Use pylint to
"Diez B. Roggisch" <[EMAIL PROTECTED]> writes:
> hg wrote:
[...]
> > In a relatively similar domain, I spent a few hours find this bug:
> >
> > value == self.Get_Value()
> > if value == WHATEVER:
> >do this
> >
> > instead of
> > value = self.Get_Value()
> > if value == WHATEVER:
> >do t
Michele Simionato wrote:
> pychecker
Thanks all ... pydev extension does not however ... will have to install
pychecker also.
hg
--
http://mail.python.org/mailman/listinfo/python-list
On Feb 27, 1:49 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> However, it might be that either pychecker or pylint will give you a warning
> for such statements.
Yep, pychecker gives a warning "Statement appears to have no effect"
Michele Simionato
--
http://mail.python.org/mailman/lis
hg wrote:
> Hi,
>
> In C/C++ I got used to write an expression like so:
>
> #define TEST 0
>
> if (TEST == value)
> {
>
> }
>
> in order to avoid the usual bug:
> if (value = TEST)
> {
>
> }
>
> In a relatively similar domain, I spent a few hours find this bug:
>
> value == self.Get_Value
Hi,
In C/C++ I got used to write an expression like so:
#define TEST 0
if (TEST == value)
{
}
in order to avoid the usual bug:
if (value = TEST)
{
}
In a relatively similar domain, I spent a few hours find this bug:
value == self.Get_Value()
if value == WHATEVER:
do this
instead of
va
