Thread: [Pydev-users] [Users] Code analysis not working in "norm...
Brought to you by:
fabioz
From: SourceForge.net <no...@so...> - 2010-05-16 17:00:37
|
The following forum message was posted by mbaas at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3711266: Hi, a while ago I realized that the code analysis feature stopped working for me. I noticed that when I had PyDev 1.5.6 installed but I can\'t say for sure when exactly it stopped working (meanwhile I have 1.5.7 installed). After playing around with several settings, new workspaces, etc. I noticed that it does actually work when I have the Python files inside a \"Source Folder\" but it does not work when they are inside a regular folder. Now I\'m wondering if that is actually a bug or a feature? I\'m sure it did work with regular folders in earlier versions as this is what I\'m always using. I wouldn\'t mind creating \"source folders\" instead of normal ones, but unfortunately, those source folders don\'t support linking to existing directories which is a feature I use all the time. So was that an intentional modification around v1.5.6 or is it just a bug? (what is the difference between a source folder and a regular one anyway? I can\'t see any difference on the file system level...?) Cheers, - Matthias - |
From: SourceForge.net <no...@so...> - 2010-05-16 19:02:40
|
The following forum message was posted by fabioz at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3711266: Actually, that\'s expected. Only files under source folders are analyzed (the source folders define your pythonpath, so, it doesn\'t make much sense analyzing a file outside of the pythonpath. Note that the source folder itself can be a link (so, you can create a regular folder and have it linked anywhere and later set that as a source folder -- what\'s not supported is having links inside of a source folder). Cheers, Fabio |
From: SourceForge.net <no...@so...> - 2010-05-17 23:04:32
|
The following forum message was posted by mbaas at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3711266: Ah, I have always only looked at the preferences but didn\'t pay attention to the project properties. I have discovered the Source Folders tab only now! I wasn\'t aware that I could just define what\'s a source folder and what\'s not. Now it makes sense and code analysis works fine again. :) Cheers, - Matthias - |
From: SourceForge.net <no...@so...> - 2010-11-26 16:01:03
|
The following forum message was posted by dhyams at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3711266: I have the same problem as the original poster, and I can't seem to figure out how to reactivate the code analysis. For example, if I go and deliberately misspell one of my imports an save the file, pydev used to highlight all instances of where I used that module as an error. It doesn't do that any more. I've verified that all of my .py files are in a source directory, and if I look at the properties for my project, pydev is there, and my project folder is listed in the "Source Folders" tab. I tried removing it and readding it, and also clicked "Force Refresh", to no avail. I also tried removing and re-adding my default interpreter. I just don't know where to look to fix the problem; I've been clicking around for quite a while now :( |
From: SourceForge.net <no...@so...> - 2010-11-27 23:41:59
|
The following forum message was posted by fabioz at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3711266: Is auto build on? (under the menu project > auto build) Cheers, Fabio |