The following forum message was posted by at http://sourceforge.net/projects/pydev/forums/forum/293649/topic/3953553:
OK, after a lot more tinkering, I fixed the problem. It looks like my issue was 2-fold: 1) Files that I had open in Eclipse before moving my workspace were re-opened after moving my workspace. They seemed to be opened just fine, but Eclipse was internally considering them to still be in my old workspace path. This was causing all kinds of internal havoc when trying to run my code. Closing and re-opening the files finally made them realize where they really were... but that didn't fix the failed import problem. 2) The failed imports I was getting when trying to run my code were because Pydev stores absolute paths internally, in files like "workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/MY_PROJECT/co m.python.pydev.analysis/AdditionalProjectInterpreterInfo.pydevinfo". Doing a "force restore internal info" on every single project in my workspace finally got rid of all the old absolute paths, and my project works again. It'd be nice if that wasn't necessary. ------------------------------------------------------------------------------ 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
