The following forum message was posted by at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3953553:
Unfortunately, I'm really not certain what actually caused the import failure to manifest, and I'm really too busy to play around with another copy of Eclipse to try to make it happen again. However, I'll try to be as specific as I can be about what I remember doing: First, I installed Eclipse 3.6 into a different folder than my 3.4 install, because I didn't want to screw up my working dev env. Then I installed the plugins my code shop uses (Aptana Studio, Pydev, Subclipse, PDT), using the usual update sites. I then tweaked some of the Eclipse settings (keybindings mostly), but I didn't touch anything related to imports of PYTHONPATH. After checking out all my projects through SVN, I realized that I needed to set up the default Python interpreter, so it set it to the MacPorts Python 2.5 install that my shop uses (the built-in Python on OSX is unsuitable for our projects). Then I started doing some dev work, and discovered the broken Globals Browser. I did several things to try and make it work, including updating to the newest nightly build (using www.pydev.org/nightly), but that didn't do anything. I *think* that using "Force restore internal info" on my project is what made the Globals Browser work, but that was when I also started getting import errors on everything outside of my project (and even things that were in the same project but under a different package tree than the erroring file). It was at that point that I deleted my workspace folder and started fresh, and I didn't have any problems after that. And thinking about that folder made me remember that at some point during that whole operation, I moved my workspace folder. I'd accidentally created it in ~/Documents/workspace-test instead of ~/dev/workspace-test). I remembered being screwed by Finder's total ignorance of .files, so instead of moving the contents of the folder, I moved the whole thing from ~/Documents to ~/dev. Maybe that's what messed it up? Something in Eclipse or Pydev may be saving absolute paths instead of workspace-relative paths. Anyway, I hope my description helps you figure out this problem. I'd hate for anyone else to go through the same frustration I suffered. ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
