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. -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
