Unlike CPython, IronPython has no Global Interpreter Lock ("GIL"), and it used unicode for strings long before that was sorted out in CPython. Differences between IronPython and CPython make IronPython a dialect, but one well-suited to multi-threaded projects. It is an excellent "glue language" as it is an interpreter with a JIT compiler; it has full access to .NET as well as to Win32; it also has access to libraries accessible through CTypes. In my day job, I write complex macros in IronPython for an application that controls exotic hardware; I prefer the IronPython read-eval-print-loop to compiling code through a heavyweight IDE and compiler that Get In My Way.
Michael Foord and Christian Muirhead, who were with Resolver Systems, wrote
an excellent book on IronPython. While its content has not been updated to address the current release, its exploration of .NET specifics makes it worth reading for the newcomer to IronPython.