Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7220558 By: fabioz
Hi, Well, the common reason why that happens is that you're probably not copying only the source files, but also the .pyc files. When the .pyc file is compiled from a source file, it adds some info from your filesystem, and that info is not recreated unless the file actually changes (but it doesn't see that you moved the file around)... So, the debugger actually sees the wrong path because of that .pyc file. If you clear the .pyc files, that should make it work (right click the source folder > pydev > clear .pyc files) Another option is not copying the .pyc files. Usually, when I have to move the code like you're doing, I use something a DVCS (e.g.: Mercurial), adding only the source files... (you could also always use it from the usb, mounting it with the same letter, so, you wouldn't have to copy it around because you'd always be working in the USB -- but you should have a version control system anyways). Cheers, Fabio ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Pydev-users mailing list Pydev-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-users
