IronPython RC1 released!

Hot off the press! IronPython RC1 has been released. If you haven't played with it yet, you really should.

IronPython 1.0 is supposed to be compatible with CPython 2.4, so if you have any CPython 2.4 application, you should be able to port it to IronPython with minimum re-work.

Let me know how it go for you! 🙂

Comments (4)

  1. Mike says:

    Kathy are you involved in this project? Do you know if this would compile?

  2. KathyKam says:

    It’s open source, so I better not touch it. But the description says it works on Python 2.4 and higher, so it should. If you run into any problems let me know. 🙂

  3. Michael Urman says:

    Where does one start the porting process? I have a library that works fine on Windows and Linux CPython2.4, but I can’t even import in in IronPython due to the lack of the normal library. I tried pointing IP’s sys.path at CPython’s libraries, but either I missed one or that doesn’t work. The particular offender was the mmap module.

  4. DinoV says:

    There are some built-in modules that IronPython doesn’t implement because .NET doesn’t expose the underlying functionality or in some cases because those modules were a lower priority.  

    In this case mmap is a built-in module and .NET doesn’t expose memory mapped files to managed code – though it would be possible to create such support using P/Invoke.  We’ve avoided using P/Invoke to ensure that IronPython has maximum portability.  One nice thing about IronPython is it’s easy to plug in your own modules and you (or someone else) could write the mmap module as it’s fairly simple and plug that until .NET supports this functionality or we add the appropriate P/Invoke’s to IronPython.

Skip to main content