Saturday, June 25, 2005

Little updates

Well, I in the last weeks I fixed many bugs, so a new release should be out pretty soon...

The bad thing is that I didn't even get near the debugger (and I was hoping someone else would fix its bugs...)

I've also worked more at home, so I'm not synchronizing very much with the cvs (my connection is pretty bad) - in case someone tried to get the code...

The good thing is that pydev has been around the most active projects in sourceforge, so it makes me fell good about the project...



Wednesday, June 15, 2005

0.9.4 release

Last release already out for some time now...

The biggest difference is the new way to configure the pythonpath... I hope you like it!!!

The thing I foud more impressive is that there were only few bugs regarding this implementation -- I was actually waiting for more :-)

So, hope to fix those in not a long time from now... and get ready for 1.0

Also, I wrote all this with a dvorak layout!!! Things are going really slow, but I'll give it a shot for some more time!!!



Wednesday, June 08, 2005

Almost ready to go

Well, most new implementations are already ready to go, so, what is missing is just updating the documentation...

After that, I'm probably only going to make bug-corrections until 1.0!

Wednesday, June 01, 2005

New PYTHONPATH configuration!!

The new pythonpath configuration is almost finished (already fully functional for code completion).

The current state is:

- Interpreter configuration: we specify an interpreter and it shows:
- the system libraries (folders) and the compiled libraries (dlls).
- the 'forced' builtin libs (this is, libraries that exist only at runtime, but don't have a specific source file associated or have but there is too much information we can only get at runtime. E.g.: os is a file ( but its information is only useful at runtime because it is too dependent on the system where it is ran. This is the case where simple AST analysis is almost useless).

Note that those that have dlls found (e.g.: qt.pyd for qt) do not have to be specified here.

- Project configuration: we specify:
- the source folders in the project
- external libraries (those that are not within any project)
- referenced projects (projects the current project depends on)
(previously, we had to re-specify everything for each project, and it didn't synchronize information that was not in the current module, and it saves a lot of memory, since we have n entities that talk with each other now -- one is the one that controls the system configuration, and the others are the ones that control the project, and talk with each other for referencing).

As I said, it is already fully functional for code completion, but PyLint, refactoring and other tools that run outside of the 'java' real environment are still not completely integrated with this new configuration (and a new build will only be released when this is done).