Analysis windows for pep8 and pyflakes?

[Monte Milanuk]

Maybe I'm missing it... but are there windows available for displaying a hierarchical tree view of the messages from pep8 and pyflakes like there is for pylint?  Right now I've got the pylint window 'docked' (guess thats the right term) in with the Object Inspector and File Explorer windows, which is pretty handy.  Being able to see all the current warnings/errors in a tree view with the ability to collapse them is *very* nice, love it!  If that could be extended to pep8 and pyflakes (or consolidate them all in one 'Code Analysis' window) that would outstanding.

Thanks,

Monte

[Pierre Raybaut]

No, there is no tree view of pep8 or pyflakes results implemented in Spyder. 

Why is that? Because these tools are very fast and can do their job (almost) real time. So, it was tempting to show results inline (directly in the text editor with flags, underlined parts, ...). Then I rapidly added the pylint plugin and I had to implement this tree view (because from my experience with Pydev on an average machine, the inline pylint implementation was not adapted because pylint is too slow. 

Now, we could merge results from the three tools in a single tree view, indeed. It would require some work though, but that's definitely doable. 

You may open a new Issue for that (on Spyder's GoogleCode website). 

Cheers,

-Pierre 

--
You received this message because you are subscribed to the Google Groups "spyder" group.
To view this discussion on the web visit https://groups.google.com/d/msg/spyderlib/-/VKxJ4uOzKyUJ.
To post to this group, send email to spyd...@googlegroups.com.
To unsubscribe from this group, send email to spyderlib+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.

[Monte Milanuk]

On 01/06/2013 01:21 PM, Pierre Raybaut wrote:

> Now, we could merge results from the three tools in a single tree view,
> indeed. It would require some work though, but that's definitely doable.

One thing that would help is some sort of marker or code to be able to
tell at a glance which analysis tool generated the message - pylint,
pyflakes, pep8, etc. As an example, right now I'm looking at some code
from a book that was done in a very consistent style, albeit not one
that necessarily shows 'clean' in pylint or pep8. After cleaning up 99%
of the things that generate errors, or else disabling them with #pylint
disable= codes... I still have two markers in the margins. One, is from
pylint (the one remaining 'error' that it can't parse) and the other...
well since I specifically disabled the pylint message code for that one,
I'm guessing its from pyflakes. The point is, the marker in the margin
just says 'Code Analysis', with no hint as to what tool generated the
message. Its still a heck of a nice thing to have, for sure.

> You may open a new Issue for that (on Spyder's GoogleCode website).

Will do.

[Pierre Raybaut]

Actually, as I wrote earlier, pylint is not integrated that way in
Spyder. Only pyflakes and pep8 show warnings in the margin. Warning
messages from pep8 are always preceded by a code (not pyflakes), so
it's quite easy to guess which one is it.

Although I agree that it would be cleaner to clearly indicate
"pyflakes" or "pep8" instead of "Code analysis" (or "Code analysis
(pyflakes)", ...).

...another "Issue"?

-Pierre

>
>> You may open a new Issue for that (on Spyder's GoogleCode website).
>
> Will do.
>

> --
> You received this message because you are subscribed to the Google Groups "spyder" group.