IronPython 1.1.2 Released

By Michael Foord -
Congratulations to the IronPython team for another great release. IronPython 1 targets Python 2.4 compatibility and version 1.1.2 is intended to be the last release of IronPython 1.
This release fixes around twenty issues from Codeplex and includes the implementation of the _winreg module plus some performance improvements.

Notable changes / bugfixes in this release include:
  • nt.unlink will now throw an exception if the file doesn’t exist, as it does in CPython
  • The signature of IronPython.Runtime.Operations.Ops.Id() has changed and it now returns an object instead of long. This maps to the id() function in Python. Note that there is no change for Python caused by this and only code which is directly calling Ops.Id from a statically typed language like C# or VB will be affected
  • Tuple hashing improvements - if you use tuples as dictionary keys you'll see a performance improvement from this
  • Backport fix for compiled regular expressions - more performance improvements - compiled regexes weren't actually compiled previously
  • Event handlers can cause circular references and leak memory - Nice to see this fixed, no need to manually unhook event handlers when disposing of UI objects now (hopefully)

The following CodePlex Work Items were also closed:
  • 16368 1.1.2: nt.access is missing
  • 15105 1.1.2: endpos is zero in IronPython 1.1.1
  • 16337 1.1.2: Trivial: Implement float.__lt__(float)
  • 16338 1.1.2: Using lambda in class definition will add into the
  • 16342 1.1.2: calling base class __call__ invokes constructor instead
  • 16343 1.1.2: problem with __slots__ and __init__ in new-style classes
  • 16347 1.1.2: Trivial: popen shouldn't open new window
  • 16348 1.1.2: Removes the inexistent file did not throw OSError in IP
  • 16350 1.1.2: int() doesn't convert representable longs to int
  • 16351 1.1.2: dict.update doesn't take keyword arguments - differs from CPython
  • 16353 1.1.2: Trivial: int('0x20', 16) fails to parse, long too
  • 16355 1.1.2: unpacking single element tuples in for-statement, listcomp and generator
  • 16356 1.1.2: socket.getnameinfo(...) broken under Vista
  • 16360 1.1.2: Class with slots and getattr not compatible
  • 16363 1.1.2: Can't call method w/ nullable as 1st argument w/ greater than 5 arguments
  • 16366 1.1.2: PyCF_DONT_IMPLY_DEDENT support in compile
  • 16749 1.1.2 (Trivial): Modifier of PythonEngine.DefaultCompilerContext(..)

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