Corruption in Code Checking?
Brought to you by:
fabioz
Menu
▾
▴
I'm getting very odd behavior out of pydev lately. Specifically I will get error reports from the code check (the little red x's in the left margin that quote lines of code that are NOT anywhere near the line being referenced! It seems that what I see displayed as code is no longer what the pydev code checking sees!
Coupled with this I am getting weird behavior where I can not successfully set breakpoints in some places even though I can step through those places if I manage a breakpoint earlier.
I'm thinking these are correlated (confusion in where user thinks code is placed in editor and where pydev does).
Making it pretty impossible to debug well anymore :-(
Is there some cleansing or rebuilding I can do to address this issue? Using Python 2.5 in eclipse 3.4.0 under pydev 2.5? (not quite sure what version of pydev.. how do I check?) (I got the version as latest in the fall of 2008).
Thanks
As a followup I routinely copy over my src folder from my pc HD to a USB to work on in a different but symmetrical workspace. Is this perhaps bad practice leading to some confusion between the workspaces?
Thanks,
Lin
I'm supposing you are using pydev extensions (and those errors are from the pydev extensions code analysis). There was a bug in which the analysis requests really got out of date, but this has been already fixed (I think it was on 1.4.3).
I'd recommend updating to the latest nightly build which is pretty stable -- it's already been quite tested and should be the released version -- which should happen in the beginning of the next week -- see: http://pydev.blogspot.com/2009/03/new-pydev-release-soon-call-for-testers.html
Cheers,
Fabio
p.s. if it still happens, please report a bug (providing some steps on how to reproduce it).
Thanks I did do an update and for now this issue has gone away.