Controlling PyDev Analysis

I'm starting work on Sage which is a pretty huge system including some 200+K lines of Python.

A very interesting feature of sage is it "all" comes with the tarball... you "could" do a regular type install, but there are a lot of dependencies and its standard practice to grab the tarball, unwind it, and type make... come back an hour later and type make test... then come back in another hour.  (they have some parallel make stuff which will make this faster... but my point is, this is a really big package given the number of other packages they provide)

As it stands, there is a great deal of replication with other stuff I have installed... when I import the project I get between 3K and 7K errors/warnings due to multiple definitions... which is correct from a "what Pydev" does perspective.

Seems like there "might" be a way to manage this.  Clearly, I could reinstall PyDev and just have it point to the sage subdirs and be done... but that hobbles my other work.

As the "default" install of PyDev kinda looks through everything, and I'd like to use stuff in my standard path, and have all of sage as well... I guess I'm wondering what "knobs" I have to control how PyDev / Extensions does its thing in this case.

This may be a corner case and it may be smarter to just have multiple eclipse/pydev installs... which will probably work.  But I was wondering if there isn't something better.

If not, thats cool too.  I think Sage has a pretty non-traditional way of doing things

-glenn