> -----Original Message----- > From: Fabio Zadrozny [mailto:fabi...@gmail.com] > Sent: den 4 februari 2010 18:03 > To: pydev-users@lists.sourceforge.net > Subject: Re: [Pydev-users] Treatment of external sources within the > workspace > > 2010/2/4 Rickard Petzäll <rickard.petz...@jeppesen.com>: > > Hello, > > > > I am looking at the problem of setting up Pydev where I have a number > of > > files part of the project and a large number of files that are really > only > > to consider as a library. The current set-up is that "my" files are > in the > > "Source Folders", and "their"(=library) files are in the "External > > Libraries". > > > > > > > > Now, a large number of legacy Python code exist in the library that > relies > > on C modules that are not loadable. This cause a problem, which it > took me > > quite a while to find out the reason for, namely that code analysis > is run > > on the library -- of course generating thousands of error markers. > > > > > > > > The obvious choice is to include the magic string > (@PydevCodeAnalysisIgnore) > > in all files that should skip analysis. But I think that in many > cases that > > is not possible, or at least cumbersome. Consider, for example, a > large > > number of files in a third party RCS. > > > > > > > > The solution is simple: I just move out the external sources outside > of the > > project hierarchy, so that Eclipse no longer considers them as > Resources. No > > analysis will be made for these resources anymore, but they will > still > > resolve thanks to the "External Libraries" record. > > > > > > > > Which leaves me at the question: Is there any particular reason for > this > > behavior? It was not what I as a user would have expected to happen. > (I > > suppose for some users, it is also not always possible to move > external > > sources away, for example when the files are part of a build process > that is > > hard to change.) > > > > The problem is that Pydev will analyze any file that's in your eclipse > project in the PYTHONPATH (source folder or external library)... The > idea is that you should only keep the files you're changing in the > project... Other dependencies should be somewhere else. If you really > want to keep them in an eclipse project but don't want to analyze > them, an option might be adding them in a .zip file (although I > haven't tested it). > > Still, if that's a common scenario, I agree that this could be changed > (it's really a bit strange that things in the external libraries are > analyzed, so, feel free to open a bug-request for that). > > Cheers, > > Fabio >
Thank you for the quick response! Bug filed, https://sourceforge.net/tracker/?func=detail&aid=2946047&group_id=85796&atid=577329 Cheers, Rickard ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
