A Good Mix 5: Cookbook entries, ADODBAPI and IronPython with Asterisk

By Michael Foord -
Only the finest selection of articles and blog posts on IronPython and related topics.
A recipe in the IronPython Cookbook showing how you can prompt the user for a connection string (for connecting to databases) using a built-in connection string editor dialog box from the Microsoft .NET Framework.
A blog entry demonstrating the power of the interactive interpreter for exploring new libraries. This entry investigates AmiConnector, which is a .NET library for working with the Asterisk Manager.
Dave Fugate, IronPython testing and infrastructure guy, pays homage to Vernon Cole for pywin32's adodbapi which runs under both CPython and IronPython. The tests have now been added to the IronPython test infrastructure so that the IronPython team will get early warning if they break it. Dave comments "Now I just need to setup Northwind databases on 40+ test machines...".
Another IronPython cookbook recipe and a very cute hack. This shows you to how to make your IronPython and Python scripts 'self-executing' on Windows by renaming them as .bat or .cmd files and adding a sprinkling of magic at the start.
A hyperbolic entry on the soberly named "Python conquers the universe" blog declaring that IronPython rather than Powershell is the future of Windows scripting:
So PowerShell is here, and it works. But its really ugly. (Your aesthetic tastes may vary.) Why, I wondered, didn't they just use Python? Mr. Payette even says that one of the goals of PowerScript was to "support a more conventional scripting experience ... [as in] VBScript, Perl, or Python."

I don't know. PowerShell development began a long time ago, before Python was as widely recognized as it is now. Maybe that just wasn't a live option at the time the project began.

But — and this is my point — it is now. Python, in the form of IronPython, is an elegant scripting language that talks .NET and can access all of .NET's libraries. It is what PowerShell could have been, should have been, would have been if events had played out just a bit differently.

So it seems to me that IronPython has bypassed PowerShell. I can't imagine using PowerShell if I had access to IronPython.

So my prediction is that PowerShell will never gain much traction. In contrast, IronPython will gain a lot of traction - more than anybody ever expected — and become the de facto Windows scripting language.

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...
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