Ok, the next release is taking some more time than usual, but that's because I'll be out next week, and I don't want to make a release before I come back -- making a release and not being able to support it the week after is usually not good -- and also, the current release is pretty stable...
Ok, there are some bugs, but the most annoying already have descriptions on how to fix them with the current release:
- Jython debugger halting: link to sourceforge bug
- Not being able to configure interpreter: link to sourceforge bug
So, the next release is targeted to the end of this month. It will focus a lot on those little details -- that can usually make programming much more enjoyable -- and some bug-fixes (as usual).
Tuesday, August 14, 2007
Wednesday, July 18, 2007
Pydev 1.3.7 and 1.3.8
Well, I didn't blog about 1.3.7 before -- and now 1.3.8 is already out ;-)
Both releases are pretty much focused on bug-fixing, solving some issues regarding the integration with Eclipse 3.3 and java 1.6.
Other noteworthy things are:
The code-completion engine uses some more heuristics for type inference (together with some other approaches -- which are pretty much the same thing). So, the following is now considered:
- Python: assert isinstance(xxx, Class)
- PyProtocols: adapt(obj, Class)
- Zope: assert Interface.implementedBy(obj)
And the Pydev Extensions Code-Analysis now detects mixing of tabs/spaces.
Both releases are pretty much focused on bug-fixing, solving some issues regarding the integration with Eclipse 3.3 and java 1.6.
Other noteworthy things are:
The code-completion engine uses some more heuristics for type inference (together with some other approaches -- which are pretty much the same thing). So, the following is now considered:
- Python: assert isinstance(xxx, Class)
- PyProtocols: adapt(obj, Class)
- Zope: assert Interface.implementedBy(obj)
And the Pydev Extensions Code-Analysis now detects mixing of tabs/spaces.
Thursday, July 05, 2007
Problems in pydev 1.3.6
Ok, there have been some reports of errors in 1.3.6
It's still the same error that should be actually fixed in 1.3.6 -- the builtins completions are not always there (and another problem that seems related to mylyn).
This should be fixed in the next release (which should be out in the beggining of the next week -- together with the integration for mylyn and support for eclipse 3.3).
So, if possible, it's reccomended to keep with Eclipse 3.2.x and pydev 1.3.4 until that release comes out.
It's still the same error that should be actually fixed in 1.3.6 -- the builtins completions are not always there (and another problem that seems related to mylyn).
This should be fixed in the next release (which should be out in the beggining of the next week -- together with the integration for mylyn and support for eclipse 3.3).
So, if possible, it's reccomended to keep with Eclipse 3.2.x and pydev 1.3.4 until that release comes out.
Friday, June 29, 2007
Pydev 1.3.6 Released
This was mainly a bug-fix release.
The major problem was that in new configurations it would not set the forced builtins correctly internally. The effect was that no builtins would appear in code-completion or when doing code-analysis.
Aside from that, a patch provided by Carl Robinson allows users to config PyLint severities.
The major problem was that in new configurations it would not set the forced builtins correctly internally. The effect was that no builtins would appear in code-completion or when doing code-analysis.
Aside from that, a patch provided by Carl Robinson allows users to config PyLint severities.
Wednesday, June 27, 2007
Pydev and JDT (SDK not required anymore)
I forgot to mention about it... Pydev 1.3.5 does not require JDT to work anymore (it's set as an optional dependency, only needed for jython development), so, users that are interested only in python can download the Eclipse Platform Runtime Binary instead of the whole SDK.
There's only one minor problem with that: the platform does not include the Error Log (which is usually useful when something goes wrong for bug reports) -- so, if you're using only the runtime and not the whole SDK, you need to look through the .metadata/.log file for those errors.
Another option is getting only the plugin that adds the error log view: org.eclipse.pde.runtime_XXX.jar -- it's pretty small (147kb here), but it needs to be gotten in the SDK.
There's only one minor problem with that: the platform does not include the Error Log (which is usually useful when something goes wrong for bug reports) -- so, if you're using only the runtime and not the whole SDK, you need to look through the .metadata/.log file for those errors.
Another option is getting only the plugin that adds the error log view: org.eclipse.pde.runtime_XXX.jar -- it's pretty small (147kb here), but it needs to be gotten in the SDK.
Subscribe to:
Posts (Atom)