Davy's IronPython Editor

By Michael Foord -
One thing that isn't clear when working with IronPython (as if it was clear for Python) is which IDE to use. The Visual Studio 2008 integration is done through IronPython Studio. This has impressive elements - but also plenty of rough edges and in my opinion isn't stable enough for regular use. IronPython Studio is built on IronPython 1 and seems to be little more than abandonware from the company that produced it.

It is not necessary to use IronPython Studio to debug IronPython code in Visual Studio, however if you want features you're used to in a Python IDE (autocomplete, go to definition, call tips, integrated interactive interpreter and so on) then you probably want to look elsewhere. I use the capable Wing IDE, but a custom solution for IronPython would be an interesting project.

This is where Davy Mitchell steps in with a new project called Davy's IronPython editor.

The screenshot below shows the editor pane (implemented with the Windows Forms SyntaxBox component) and the class browser.


You can download Davy's IronPython Editor from its Google code project page:
The project intentions is to create a editor along the lines of SPE or DrPython for the IronPython world. DIE is easy to deploy (zero install) and will run from a USB key etc.

This project is targeted at IronPython 2.0 and is developed on the Windows Platform. Currently it uses the SyntaxBox component (LGPL) for the text editing component.

Comments

Post a Comment

Popular posts from this blog

Extending Abobe Flash Player and AIR with Python and Ruby

By Michael Foord -
An intriguing blog entry about an Adobe experimental project. It is a C/C++ cross- compiler for the flash player and AIR. This means that you can (will be able to?) cross-compile the Python / Ruby/ lots of other language runtimes and then run them in Flash. The blog entry contrasts this approach to the DLR which requires the re-implementation of dynamic languages - hence IronPython and IronRuby. The project is already beyond proof-of concept, they even have Quake III cross-compiled and running in Flash. Extending Adobe Flash Player and AIR with C/C++ Cross-Compiler Quake 3 has already been ported to managed code , but this is even more impressive. Whether the Python interpreter can be cross-compiled to run on top of another runtime (with completely different basic types), without changing the language semantics at all, has yet to be proved - but it is a very interesting project. (It also means that Python/Ruby will possibly be enabled only by additional optional downloads - but don'
Read more

IronPython Tools for Visual Studio CTP3

By Michael Foord -
At PyCon this year Dino Veihland announced IronPython Tools for Visual Studio, an extension to Visual Studio 2010 for working with IronPython. It features Python syntax highlighting, awesome auto-complete (intellisense) and a host of other features for working with IronPython code in Visual Studio. It can be used with the free Visual Studio shell and doesn't require you to own a full copy of Visual Studio. The third CTP (Community Technology Preview) has been made available for download. IronPython Tools for Visual Studio We are happy to announce a minor update to the IronPython Tools for Visual Studio.  IronPython Tools for Visual Studio (IPyTools) is a set of extensions available for Visual Studio 2010 which supports development of IronPython applications.  This release is our 3rd Community Technical Preview (CTP) and builds upon the previous two releases.  The release is a minor update which includes bug fixes and a number of small features.  You can download the latest rel
Read more

Further Adventures of the Debugger

By Michael Foord -
Harry Pierson (Microsoft IronPython PM) has been experimenting with writing an IronPython debugger ( ipydbg ) on top of the .NET MDbg APIs. When we last left him , he had implemented Just My Code (JMC) support allowing you to step into IronPython code. Since then he has made a lot of progress including a colourful REPL (interactive console) and solving some difficult problems around getting to real values behind boxed IronPython variables (needed for showing local variables). He has blogged extensively on what he has been up to (more recent posts last): Showing Source Code Colorful Console IronPython ConsoleColorMgr (the colorful console code pulled out into a separate IronPython module) A Little Hack...err...Cleanup Getting Local Variables Displaying Values Command Routing Getting Arguments REPL Console A lot of functionality is now present. In the command routing entry Harry outlines the seven commands supported by the debugger so far: Continue, Quit, Show Stack Trace, Show Locals,
Read more