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.
AmiConnector, which is a .NET library for working with the Asterisk Manager.
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...".
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.