I haven’t tried out the last few betas of IronPython because of a lack of time, but getting it to work with our application will a priority for me latter this summer. So today I decided to take a wack at Beta7.

I first tried to get it to use our DLL’s but that wasn’t working. I broke down and looked at the docs and they added the AddReferenceToFileAndPath to the clr library. That’s what they recommend for scripts now instead of Beta1′s AddReference. After changing that, things were working wonderfully! Even better — Beta7 can load ConfigParser, which Beta1 couldn’t (yes, I filed the bug on that one). That is a Good Thing(tm) for me, since I use ConfigParser a lot in my scripts at work.

The big test was making it work with the most-excellent path module. Not just because I use it alot, but also because it combines a lot of standard Python modules together. If path works, it implies that os.path, glob, and even shutil are all working.

And the initial verdict is good:

IronPython 1.0.60523 (Beta) on .NET 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
>>> from path import path
>>> parent = path("..")
>>> for dll in parent.glob("*.dll"):
...    print dll
...
..\IronMath.dll
..\IronPython.dll
..\MSEDAF.dll
..\MSEL.dll
..\WPOBJAPILib.dll
>>>

Let the banging-the-crap-out-of-it continue!