On Oct 30, 8:53 am, Bruno Desthuilliers wrote:
> Robert Kern a écrit :> On 2009-10-29 16:52 PM, Aahz wrote:
> (snip)
> >> Coincidentally, I tried PyFlakes yesterday and was unimpressed with the
> >> way it doesn't work with "import *".
>
> > I consider "import *" the first error to be fixed, so it
On 10/29/09 9:48 PM, kj wrote:
> How can one check that a Python script is lexically correct?
You can use a pseudo-static analyzer like pyflakes, pylint or pydoctor.
Or, better, you can avoid wild imports, excessive local or global
namespace manipulation, and break you program in smaller parts an
On Thu, Oct 29, 2009 at 6:48 PM, kj wrote:
>
> How can one check that a Python script is lexically correct?
>
> As my Python apps grow in complexity and execution, I'm finding it
> more often the situation in which a program dies after a lengthy
> (i.e. expensive) run because the execution reaches
Aahz wrote:
In article ,
Robert Kern wrote:
I like using pyflakes. It catches most of these kinds of typo errors, but is
much faster than pylint or pychecker.
Coincidentally, I tried PyFlakes yesterday and was unimpressed with the
way it doesn't work with "import *".
If only IDLE's Intell
Robert Kern a écrit :
On 2009-10-29 16:52 PM, Aahz wrote:
(snip)
Coincidentally, I tried PyFlakes yesterday and was unimpressed with the
way it doesn't work with "import *".
I consider "import *" the first error to be fixed, so it doesn't bother
me much. :-)
+1 QOTW
--
http://mail.python.
kj wrote:
> As my Python apps grow in complexity and execution, I'm finding it
> more often the situation in which a program dies after a lengthy
> (i.e. expensive) run because the execution reaches, say, a typo.
This is a good reason for breaking your program down into testable
units and verifyi
Albert Hopkins writes:
> On Thu, 2009-10-29 at 17:27 -0500, Robert Kern wrote:
> > I consider "import *" the first error to be fixed, so it doesn't
> > bother me much. :-)
>
> But does pyflakes at least *warn* about the use of "import *" (I've
> never used it so just asking)?
That's easy enough
On Thu, 2009-10-29 at 17:27 -0500, Robert Kern wrote:
> I consider "import *" the first error to be fixed, so it doesn't
> bother me much. :-)
But does pyflakes at least *warn* about the use of "import *" (I've
never used it so just asking)?
--
http://mail.python.org/mailman/listinfo/python-li
[email protected] (Aahz) writes:
> Coincidentally, I tried PyFlakes yesterday and was unimpressed with
> the way it doesn't work with "import *".
That's pretty much the reason to avoid ‘from foo import *’: it makes the
namespace indeterminate without actually running the code. Just as much
a p
On 09:52 pm, [email protected] wrote:
In article ,
Robert Kern wrote:
I like using pyflakes. It catches most of these kinds of typo errors,
but is
much faster than pylint or pychecker.
Coincidentally, I tried PyFlakes yesterday and was unimpressed with the
way it doesn't work with "imp
On 2009-10-29 16:52 PM, Aahz wrote:
In article,
Robert Kern wrote:
I like using pyflakes. It catches most of these kinds of typo errors, but is
much faster than pylint or pychecker.
Coincidentally, I tried PyFlakes yesterday and was unimpressed with the
way it doesn't work with "import *".
In article ,
Robert Kern wrote:
>
>I like using pyflakes. It catches most of these kinds of typo errors, but is
>much faster than pylint or pychecker.
Coincidentally, I tried PyFlakes yesterday and was unimpressed with the
way it doesn't work with "import *".
--
Aahz ([email protected])
On 2009-10-29 15:48 PM, kj wrote:
How can one check that a Python script is lexically correct?
As my Python apps grow in complexity and execution, I'm finding it
more often the situation in which a program dies after a lengthy
(i.e. expensive) run because the execution reaches, say, a typo.
Of
kj schrieb:
How can one check that a Python script is lexically correct?
As my Python apps grow in complexity and execution, I'm finding it
more often the situation in which a program dies after a lengthy
(i.e. expensive) run because the execution reaches, say, a typo.
Of course, this typo needs
kj wrote:
> How can one check that a Python script is lexically correct?
By using pylint.
Mick.
--
http://mail.python.org/mailman/listinfo/python-list
There are several static analysis tools that can check whether a variable
name is used before it is defined.
At my old workplace we used "pylint", so I can recommend that:
http://www.logilab.org/857
--Daniel
--
http://mail.python.org/mailman/listinfo/python-list
How can one check that a Python script is lexically correct?
As my Python apps grow in complexity and execution, I'm finding it
more often the situation in which a program dies after a lengthy
(i.e. expensive) run because the execution reaches, say, a typo.
Of course, this typo needs to be fixed
17 matches
Mail list logo
