FePy the community distribution of IronPython.
The blog entry focuses on the differences between how CPython (the reference implementation) and IronPython do encoding name normalisation in the codecs module.
So Python normalizes encoding names received from codecs.lookup. How exactly this is done isn't really specified.
But did you know that the following code work with CPython? (I don't recommend this!!!)
Yes, those are three exclamation marks. I'm not kidding...
The IronPython and IronRuby teams will find some serious versioning issues as they try to manage the DLR versioning story between themselves and the CLR as a whole. An initial hack will result, which will be codified into a standard practice when .NET 4.0 ships. Then the next release of IPy or IRb will have to try and slip around its restrictions in 2010/2011. By 2012, IPy and IRb will have to be shipping as part of Visual Studio just to put the releases back into lockstep with one another (and the rest of the .NET universe).
This year, I hope to get my IronPython resources section together here on CodingGeekette.com and blog about it a bit more. I will be talking about IronPython at CodeMash, PyCon, and quite possibly PyOhio. If other people want to hear me talk on it, just send me an email at sarah at codinggeekette dot comIronclad, shows how to load assemblies and import from them, and also has handy hints for using the Python logging module and working with the Windows registry. He also talks about turning IronPython programs into binary executables with the Pyc compiler.
This collection of posts hasn't included much actual code, so the next one will be more focused on practical examples with IronPython.