Monday, December 22, 2008
Pydev 1.4.1
Ok, after 1.4 a bug was found dealing with the licensing (for Pydev Extensions on Eclipse 3.4.1), so, this release fixes this one bug (so, it's only released again in fabioz.com, not on sourceforge).
Pydev 1.4
Yeap, Pydev 1.4 It's finally out ;-)
Major things include:
- Support for Python 3.0 and Python 2.6
- The context-based find definition was moved from Pydev Extensions to Pydev Open source (note that the context-independent part, which goes on to find a definition from all the available tokens in your workspace is still only available in Pydev Extensions)
- A major bug was fixed in the parser when multiple threads were making the parse (this became more evident in java 6 with its optimizations, so, if you found out you had warnings that sometimes appeared nonsense, it should be fixed now)
- Hovers were added for docstrings and to show variables when debugging
Aside from that, there are a bunch of other bugfixes available.
Note that there are some things that are probably still missing to say that the Python 3.0 support is a 100% finished (most notably, the coverage is still not available because the coverage.py module used still does not support it... so, it's waiting on that to properly support it) and as it's a really big change, there's probably a bunch of other things that are still missing... so, I'm waiting on the bug reports :)
Major things include:
- Support for Python 3.0 and Python 2.6
- The context-based find definition was moved from Pydev Extensions to Pydev Open source (note that the context-independent part, which goes on to find a definition from all the available tokens in your workspace is still only available in Pydev Extensions)
- A major bug was fixed in the parser when multiple threads were making the parse (this became more evident in java 6 with its optimizations, so, if you found out you had warnings that sometimes appeared nonsense, it should be fixed now)
- Hovers were added for docstrings and to show variables when debugging
Aside from that, there are a bunch of other bugfixes available.
Note that there are some things that are probably still missing to say that the Python 3.0 support is a 100% finished (most notably, the coverage is still not available because the coverage.py module used still does not support it... so, it's waiting on that to properly support it) and as it's a really big change, there's probably a bunch of other things that are still missing... so, I'm waiting on the bug reports :)
Saturday, December 20, 2008
Pydev: Python 2.6/3.0 support status
Finished topics on the support for Python 2.6 and Python 3.0:
- The grammar support is finished (a lot of work was done at this area, as the grammar changed quite a bit -- a good side-effect of that is that as I spent more time dealing with JavaCC and the AST construction, some good cleanups were done, and the parsing of all versions should be a bit faster now)
- Interpreter can be configured for those
- The project config can use the new grammars
- Code-completion is working
- Pretty printing of the new grammar seems to be complete
Things unfinished are:
- Debugger
- Unbuffered support (apparently, passing -u to the interpreter does not give unbuffered output anymore -- which is probably a regression bug), so, an acceptable workaround still needs to be found.
- Code coverage
- Code analysis must be checked with the new constructs
That's it... that support should finished pretty soon ;-)
- The grammar support is finished (a lot of work was done at this area, as the grammar changed quite a bit -- a good side-effect of that is that as I spent more time dealing with JavaCC and the AST construction, some good cleanups were done, and the parsing of all versions should be a bit faster now)
- Interpreter can be configured for those
- The project config can use the new grammars
- Code-completion is working
- Pretty printing of the new grammar seems to be complete
Things unfinished are:
- Debugger
- Unbuffered support (apparently, passing -u to the interpreter does not give unbuffered output anymore -- which is probably a regression bug), so, an acceptable workaround still needs to be found.
- Code coverage
- Code analysis must be checked with the new constructs
That's it... that support should finished pretty soon ;-)
Subscribe to:
Posts (Atom)