Michael Foord discusses IronPython, the DLR, dynamic languages on .Net, static vs. dynamic typing, Visual Studio integration, Resolver One, Intellipad, Crack.net, embedding IronPython, the ScriptEngine, error handling, dynamic operations, functions as delegates, and the C# 4.0 dynamic keyword.
At RubyFringe John Lam talks about his path to dynamic languages, some of the problems of making IronRuby run fast, and how the DLR helps with implementing languages.
Python Tools for Visual Studio, which has its first production release today, now supports all four major Python interpreters, CPython, IronPython, Jython, and PyPy. It is available with the free Visual Studio Integrated Shell or as a plugin for Visual Studio Professional.
Microsoft’s Developer Division has released a release candidate of Python Tools for Visual Studio. In addition to supporting refactoring in CPython and IronPython, this release offers support for MPI (Message Passing Interface) and Microsoft HPC (High Performance Computing). Visual Studio Ultimate owners also get a profiler for CPython.
As part of the Python Tools for Visual Studio project the well-known NumPy and SciPy libraries were ported to .NET. The port, which combines C# and C interfaces over a native C core, was done in such a way that all .NET languages can take advantage of it.
Microsoft Technical Computing Group has just announced the Python Tools for Visual Studio (PTVS) open source project. PTVS improves on the IronPython Tools for Visual Studio code base (introduced in IronPython 2.7) and adds CPython, Cluster support and new modules like NumPy and SciPy in .Net.
IronPython 2.7 has been released with new features including improved tooling inside Visual Studio, better interoperability with LINQ and extension methods, better documentation, and full language parity with Python 2.7.
Last week Miguel de Icaza published a long post listing all the work the Mono team at Novell has been doing since the move to GitHub in July 2010. Much of the new work has been around language development and MonoDevelop improvements.
Since Microsoft announced that it was giving up control of its Iron languages, there has been a quiet debate on where to host the project. The negotiations have finally been settled and the winner is Github for source control and CodePlex for issue tracking.
