Re: [Pydev-users] Code Analysis
Brought to you by:
fabioz
From: Nikolaus R. <Nik...@ra...> - 2009-06-23 00:08:28
|
Fabio Zadrozny <fa...@gm...> writes: >> I am currently testing the code analysis offered by Pydev Extensions. I >> think I really like the analysis itself (it directly showed me quite >> some places where I could clean up and improve my code), but I am >> confused by what exactly is included in the analysis: >> >> Sometimes I get errors and warnings from a file only after I have opened >> it, so I concluded that code analysis is only done on open files. >> >> Then, however, I tried get rid of a couple of errors by closing the >> respective file (expecting this would exclude it from the code >> analysis). However, the errors are still shown. >> >> Is there a way to have the code analysis run on all files in the >> project (no matter if currently open or not) and to exclude some >> individual files completely (again, no matter if open or not)? > > Right now it works in the following way: > > Any valid python file that maps to a python module (with __init__.py > along the way) under a source folder will be analyzed when: > - the file changes > - the file is opened > > But it won't automatically analyze all the existing files -- if you > want that you can force pydev to do so by doing a project > clean and > select which project(s) should have the files analyzed. That makes sense, thanks a lot. Just to make it absolutely clear: what exactly does it mean for a file to "map to a python module"? > The only way to ignore a file under the pythonpath in the analysis is > by adding a comment: #@PydevCodeAnalysisIgnore in the file that should > not be analyzed. Arr. Now that you say it, I also remember that I have seen that in the options window. Must have blocked that out for some reason. Thanks! -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C |