[Pyzo] Any intentions to implement a code analyzer?

[kaktus018]

Hello,
I'm working in engineering and first of all I would like to say that Pyzo
is my favorit Python IDE. I'm mostly working with Matlab and appreciate the
similar and easy workflow for projects in Pyzo - sometimes it is even more
intuitive than in Matlab (not at least because of Python). I'm absolutely
prefering it over Spyder (which feels a bit clumsy).
What I think would really help in coding is a static code analyzer. What I
think is most useful is the detection of syntax errors and 'this is defined
but never used' and 'this is used but never defined'. Using off-the-shelf
solutions like pylint is probably a licensing issue, but I would like to
ask if a code analyzer is planned in the future.

Best regards,
Dominik

[Almar Klein]

Hi Dominik,

Thanks for the feedback!

Yes, I would love static code analysis too! Along with several other
ideas that I think can make Pyzo better still. It's really a matter of
not having enough time to work on Pyzo ...

Regards,
  Almar

Post by kaktus018
Hello,
I'm working in engineering and first of all I would like to say that
Pyzo is my favorit Python IDE. I'm mostly working with Matlab and
appreciate the similar and easy workflow for projects in Pyzo -
sometimes it is even more intuitive than in Matlab (not at least
because of Python). I'm absolutely prefering it over Spyder (which
feels a bit clumsy).
What I think would really help in coding is a static code analyzer.
What I think is most useful is the detection of syntax errors and
'this is defined but never used' and 'this is used but never defined'.
Using off-the-shelf solutions like pylint is probably a licensing
issue, but I would like to ask if a code analyzer is planned in the
future.
Best regards,
Dominik
--
You received this message because you are subscribed to the Google Groups "Pyzo" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.