Well, as publicized already, Aptana was acquired by Appcelerator (http://www.appcelerator.com/appcelerator-acquires-aptana/).
So, I thought I'd write a bit about it...
First thing to note is that (as the rest of the team) I've joined Appcelerator, and the plan is to keep Pydev going forward (as it has been going since I had joined Aptana). However, unlike the rest of the team, I'm still based on Brazil :)
I think that the only difference in focus is that now, aside from the support for Django and Google App Engine, Titanium (which is Appcelerator's platform for developing desktop and mobile applications) will also have some special attention, although I still don't have more details on what exactly this means...
All in all, I think this was a good thing, as one of the things that Aptana was looking for was something to support (as the plans were always about giving Aptana Studio for free and making money on something else), and Appcelerator will have a nice improvement in terms of a better coding environment :)
Tuesday, January 18, 2011
Monday, January 03, 2011
Pydev 1.6.4 released
Pydev 1.6.4 is now available.
The major change is the new unittest support, which was previously commented at: http://pydev.blogspot.com/2010/12/improved-unittest-support-in-pydev.html
Now, there were some other changes since that post that are worth mentioning too:
The default Pydev test runner can now distribute tests among multiple processes, which can make testing much faster (if you have multiple CPUs available). Although note that if the tests weren't properly designed they may break. One example would be the case when 2 tests end up writing/reading to the same file.
Note that there's also an option to run all the tests from a given module in the same process (instead of separating them 'randomly' among processes).
See: http://pydev.org/manual_adv_pyunit.html for details on the flags to be passed to enable running in multiple processes and basic instructions on how to use the new unittest integration.
Also important is that a major bug was fixed -- in this bug, existing interpreters could end up being corrupted when a new interpreter was added (so, if you are using multiple interpreters you're strongly advised to upgrade) -- note: if there seems to be some issue with corruption of the internal pydev indexes, ctrl+2 --reindex can be used (while in the pydev editor) to ask for the pydev indexes to be rebuilt (which would be the case if the globals browser is not working properly or the pydev code analysis was manually stopped for some reason) it shouldn't be needed, but, if the need arises, it's there :)
The major change is the new unittest support, which was previously commented at: http://pydev.blogspot.com/2010/12/improved-unittest-support-in-pydev.html
Now, there were some other changes since that post that are worth mentioning too:
The default Pydev test runner can now distribute tests among multiple processes, which can make testing much faster (if you have multiple CPUs available). Although note that if the tests weren't properly designed they may break. One example would be the case when 2 tests end up writing/reading to the same file.
Note that there's also an option to run all the tests from a given module in the same process (instead of separating them 'randomly' among processes).
See: http://pydev.org/manual_adv_pyunit.html for details on the flags to be passed to enable running in multiple processes and basic instructions on how to use the new unittest integration.
Also important is that a major bug was fixed -- in this bug, existing interpreters could end up being corrupted when a new interpreter was added (so, if you are using multiple interpreters you're strongly advised to upgrade) -- note: if there seems to be some issue with corruption of the internal pydev indexes, ctrl+2 --reindex can be used (while in the pydev editor) to ask for the pydev indexes to be rebuilt (which would be the case if the globals browser is not working properly or the pydev code analysis was manually stopped for some reason) it shouldn't be needed, but, if the need arises, it's there :)
Subscribe to:
Posts (Atom)