IronPython 2.6 Release Roadmap

By Michael Foord -
Today the IronPython team put a roadmap online highlighting the major new features and an approximate time frame for betas.
New features
  • CPython 2.6 compatibility
  • Improved startup time
  • New built-in modules that were previously missing:
    • ctypes
    • heapq
New IronPython features:
  • meta-class method __clrtype__ for better .NET interop support
  • Cached subtypes
  • Adaptive interpreter (related to improved startup time)
  • New built-in profiler
  • Optional sys._getframe support
Tenative release plan
  • IronPython 2.6 Alpha 1 - Mar 26, 2009
  • At least 50% of 2.6 tests pass that passed under 2.5. Many of the big new features implemented.
  • IronPython 2.6 Beta 1 - End of May
  • Mostly feature complete - all 2.6 features, abstract interpreter, cached new types, __clrtype__, ctypes
  • IronPython 2.6 Beta 2 - ~2 months later
  • Primarily bug fixes on top of Beta 1. Also maybe some top small features as requested by users.
  • IronPython 2.6 RC 1 - ~1.5 months later
  • Build is truly a candidate for release. If no showstoppers are reported this build will be shipped as RTM
  • IronPython 2.6 Final ~1 month later.
  • Final build - same as RC1 if showstoppers are not found. Otherwise same as RC2 or if only one or two minor issues are found then RC1 + fixes.
We are also discussing on the IronPython mailing list which Codeplex issues will be looked at for an IronPython 2.0.2 release, which will hopefully be coming soon... If you have favourite bugs now is the time to speak up!

Comments

Post a Comment

Popular posts from this blog

Extending Abobe Flash Player and AIR with Python and Ruby

By Michael Foord -
An intriguing blog entry about an Adobe experimental project. It is a C/C++ cross- compiler for the flash player and AIR. This means that you can (will be able to?) cross-compile the Python / Ruby/ lots of other language runtimes and then run them in Flash. The blog entry contrasts this approach to the DLR which requires the re-implementation of dynamic languages - hence IronPython and IronRuby. The project is already beyond proof-of concept, they even have Quake III cross-compiled and running in Flash. Extending Adobe Flash Player and AIR with C/C++ Cross-Compiler Quake 3 has already been ported to managed code , but this is even more impressive. Whether the Python interpreter can be cross-compiled to run on top of another runtime (with completely different basic types), without changing the language semantics at all, has yet to be proved - but it is a very interesting project. (It also means that Python/Ruby will possibly be enabled only by additional optional downloads - but don'
Read more

Should Python Projects Support IronPython and Jython?

By Michael Foord -
The maintainers of the Spring Framework for Python ( Spring Python ) wonder how much of a priority it is to have compatibility with platforms other than CPython. In other words, should they support IronPython and Jython - and if so what should they do about their C extension dependencies? This question sparks a good discussion and is relevant to many other Python projects and applications: Need for supporting IronPython, Jython? " One of the topics on my mind recently, as we consider refactoring the core container, is how we ensure that when we introduce internal dependencies, such as possibly the Amara libraries for XML processing, what secondary constraints we might be introducing. " " For example, Amara represents a very pythonic and therefore simple to read and use approach to developing XML processing, such as our very own XML application configuration parsers. So from that perspective, things are very attractive. But then you ask the question, "can I run this
Read more

Further Adventures of the Debugger

By Michael Foord -
Harry Pierson (Microsoft IronPython PM) has been experimenting with writing an IronPython debugger ( ipydbg ) on top of the .NET MDbg APIs. When we last left him , he had implemented Just My Code (JMC) support allowing you to step into IronPython code. Since then he has made a lot of progress including a colourful REPL (interactive console) and solving some difficult problems around getting to real values behind boxed IronPython variables (needed for showing local variables). He has blogged extensively on what he has been up to (more recent posts last): Showing Source Code Colorful Console IronPython ConsoleColorMgr (the colorful console code pulled out into a separate IronPython module) A Little Hack...err...Cleanup Getting Local Variables Displaying Values Command Routing Getting Arguments REPL Console A lot of functionality is now present. In the command routing entry Harry outlines the seven commands supported by the debugger so far: Continue, Quit, Show Stack Trace, Show Locals,
Read more