Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period.
The Wayback Machine - https://sup1a9wrlpyh5li9ro.vcoronado.top/web/20100223101738/http://www.ironpython.com:80/old.html
IronPython
Original Homepage
IronPython is a new Python
implementation targeting the
.NET and
Mono platforms. It is...
Fast - IronPython-0.6 is up to 1.7x faster than Python-2.3 on the
standard pystone benchmark. An early performance report is are
contained in this paper for PyCon 2004.
Integrated with the Common Language Runtime - IronPython code can
easily use CLR libraries and Python classes can extend CLR classes.
Fully dynamic - IronPython supports an interactive interpreter
and transparent on-the-fly compilation of source files just like standard
Python.
Optionally static - IronPython also supports static compilation
of Python code to produce static executables (.exe's) that can be run
directly or static libraries (.dll's) that can be called from other CLR
languages including C#, VB, managed C++ and many more. Note: static
compilation is only partially implemented in the 0.6 public release.
This will need further development before being useful.
Managed and verifiable - IronPython generates verifiable
assemblies with no dependencies on native libraries that can run in
environments which require verifiable managed code.
Not finished - IronPython is currently at a pre-alpha stage
suitable for experimentation but not for serious development work. The
latest public release can be downloaded below.
Public Release
IronPython-0.6 is now available as Open Source Software under the
Common Public License version 1.0.
A single zip file containing both the source code and the binary executables can
be downloaded below.
After many requests there is now a mailing list to discuss IronPython.
Please use this list to share your experiences, bug reports, suggestions, or
questions.
Click
here for archives and/or to join the list.
Release Announcement from July 28, 2004
It was a little less than a year ago that I first started investigating
the Common Language Runtime (CLR). My plan was to do a little work and then
write a short pithy article called, "Why .NET is a terrible platform for
dynamic languages". My plans changed when I found the CLR to be an excellent
target for the highly dynamic Python language. Since then I've spent much of my spare time working on the development of
IronPython.
The more time that I spent with the CLR, the more excited I
became about its potential. At the same time, I was becoming more frustrated
with the slow pace of progress that I was able to make working on this project
in my spare time. After exploring many alternatives, I think that I've found the
ideal way to continue working to realize the amazing potential of the vision of
the CLR. I've decided to join the CLR team at Microsoft beginning on August 2.
At Microsoft I plan to continue the work that I've begun with IronPython to
bring the power and simplicity of dynamic/scripting languages to the CLR. My
work with Python should continue as a working example of a high-performance production
quality implementation of a dynamic language for the CLR. I will also reach
out to other languages to help overcome any hurdles that are preventing them
from targeting the CLR effectively. I welcome any and all feedback about how to
best accomplish this. You can reach me at
.
