Ok, this release is just to iron out some high-priority bugs that have been introduced in the last version.
Most notably, a bug where the pydev package explorer was not working correctly when the project root was configured as a source folder and some fixes in the debugger step return / step over (because of improvements to run those with untraced frames).
Yeap, seems that the saying "Given enough eyeballs, all bugs are shallow" is really true -- I had already been running 1.3.16 for some days here and after the release it took just a couple of hours for those bugs to be reported.
Enjoy!
Monday, May 12, 2008
Thursday, May 08, 2008
Bug in pydev package explorer (1.3.16)
Ok, a serious bug was found in the pydev package explorer... in version 1.3.16, when a project has the project root in the pythonpath, its children won't appear. For users that have a source folder within the project, this doesn't seem to happen.
This problem has just been fixed and a new release should be out pretty soon (in 1.3.17)
This problem has just been fixed and a new release should be out pretty soon (in 1.3.17)
Wednesday, May 07, 2008
Pydev 1.3.16
Yeap, it's just been released. Most of the work on this release was on bug-fixes, so, it should be safe to upgrade without major concerns.
The launching facility had some changes, mostly regarding the Ctrl+F11 when it's set to launch the current editor (it just didn't work the way it was supposed to), but that's only valid for new launch configurations (so, if you do want to use it instead of having it launch the previously launched app, existing launches should be deleted -- just note that you should delete only a few launches at a time (around 10-15) -- for some reason eclipse takes a lot of time to delete lots of launches at once (I tried doing it here and it halted for about 5 minutes until I decided to kill it and delete in small steps).
The launching facility had some changes, mostly regarding the Ctrl+F11 when it's set to launch the current editor (it just didn't work the way it was supposed to), but that's only valid for new launch configurations (so, if you do want to use it instead of having it launch the previously launched app, existing launches should be deleted -- just note that you should delete only a few launches at a time (around 10-15) -- for some reason eclipse takes a lot of time to delete lots of launches at once (I tried doing it here and it halted for about 5 minutes until I decided to kill it and delete in small steps).