Differences between revisions 1 and 27 (spanning 26 versions)
Revision 1 as of 2004-03-03 17:03:49
Size: 790
Editor: 66
Comment:
Revision 27 as of 2009-06-14 14:07:55
Size: 3364
Editor: FL1-118-111-35-196
Comment: added a reference to the book "Pro IronPython"
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
IronPython is [http://hugunin.net/index.html JimHugunin's] early-stage prototype implementation of Python on the .NET CLR. == IronPython ==
Line 3: Line 3:
Early results are promising, but as of March 2004, there have been no further updates since Jim's end-of-2003 post announcing preliminary results: http://primates.ximian.com/~miguel/ironpython IronPython is [[http://hugunin.net/index.html|JimHugunin's]] implementation of Python on the .NET CLR.
Line 5: Line 5:
These results were quite promising, showing great performance, even better than CPython 2.3 on the Pystone benchmark, but remember this is an early prototype, not a full implementation. The project has a [[http://www.codeplex.com/Wiki/View.aspx?ProjectName=IronPython|workspace]] where you can get news and download the latest version.
Line 7: Line 7:
These results caused a flurry of discussion, which has since died down, pending more information from Jim.  * Stable Version is 1.1.2 (targeting Python 2.4)
 * Developers Version is 2.0 RC1 (targeting Python 2.5)
Line 9: Line 10:
http://www.python.org/~jeremy/weblog/031209a.html
http://www.hole.fi/jajvirta/weblog/20031210T0901.html
http://primates.ximian.com/~miguel/archive/2003/Dec-09.html
Version 2 (which uses the Dynamic Language Runtime, a framework for writing dynamic languages for .NET which was abstracted out of IronPython 1) is part of Silverlight 2. This means that IronPython can be used for client-side scripting ''in the browser''.

Mozilla are working on porting the DLR (well, the underlying Core CLR that it uses in fact) to run on their Tamarin JIT. This should mean that IronPython will also run in future versions of Firefox. (See [[http://wiki.mozilla.org/Tamarin:IronMonkey|IronMonkey]]).

IronPython is actually a Python compiler. It compiles Python code to in memory assemblies before execution (which can be saved to disk, making binary only distributions possible).

Performance is comparable to CPython - much faster for some things (where it can take advantage of the JIT compiler in the underlying platform), but slower for other things (particularly the built in container types where a lot of work has been done on optimising the CPython types).

Reasons that CPython programmers might be interested in IronPython include:

 * Corporate credibility (introducing new technologies can be very difficult in some companies, if .NET is already established then you may need no excuse to start using IronPython)
 * No GlobalInterpreterLock - IronPython has ''no GIL'' and multi-threaded code can use multi core processors
 * The .NET framework library is ''very big''. Particularly the user interface library Windows Forms is very good.
 * IronPython is easy to embed in .NET applications as a scripting language
 * Easier to extend than CPython (C# is memory managed and C# types can be used directly in IronPython with no wrapping)
 * Silverlight!

A book on IronPython is now available via the Manning Early Access Program: [[http://www.ironpythoninaction.com/|IronPython in Action]].

A useful resource for IronPython code examples, is the [[http://www.ironpython.info|IronPython Cookbook]].

A book that introduces core concepts of IronPython programming using a .NET–centric approach is
[[http://www.apress.com/book/view/9781430219620|Pro IronPython]].

[[http://www.zetcode.com/tutorials/ironpythontutorial/|IronPython Winforms tutorial]] at [[http://www.zetcode.com/|ZetCode]].

== Other Python-Like Languages for .NET/Mono ==

Some other Python-like languages for .NET and Mono include:
 * BooLanguage - Syntax is very similar to Python's, yet the language is statically compiled. It implements many features that have been suggested for [[Python3.0]]. See [[http://boo.codehaus.org/Gotchas+for+Python+Users|Gotchas for Python Users]] for specific comparisons between boo and CPython.
 * [[http://cobra-language.com/|Cobra Language]]



== Accessing .NET from CPython ==

[[http://www.zope.org/Members/Brian/PythonNet/index_html|Python for .NET]] is the reverse of IronPython, it lets you access .NET assemblies from CPython.


----

See also: PythonAndParrot, LoGix, IronPython IDE

IronPython

IronPython is JimHugunin's implementation of Python on the .NET CLR.

The project has a workspace where you can get news and download the latest version.

  • Stable Version is 1.1.2 (targeting Python 2.4)
  • Developers Version is 2.0 RC1 (targeting Python 2.5)

Version 2 (which uses the Dynamic Language Runtime, a framework for writing dynamic languages for .NET which was abstracted out of IronPython 1) is part of Silverlight 2. This means that IronPython can be used for client-side scripting in the browser.

Mozilla are working on porting the DLR (well, the underlying Core CLR that it uses in fact) to run on their Tamarin JIT. This should mean that IronPython will also run in future versions of Firefox. (See IronMonkey).

IronPython is actually a Python compiler. It compiles Python code to in memory assemblies before execution (which can be saved to disk, making binary only distributions possible).

Performance is comparable to CPython - much faster for some things (where it can take advantage of the JIT compiler in the underlying platform), but slower for other things (particularly the built in container types where a lot of work has been done on optimising the CPython types).

Reasons that CPython programmers might be interested in IronPython include:

  • Corporate credibility (introducing new technologies can be very difficult in some companies, if .NET is already established then you may need no excuse to start using IronPython)

  • No GlobalInterpreterLock - IronPython has no GIL and multi-threaded code can use multi core processors

  • The .NET framework library is very big. Particularly the user interface library Windows Forms is very good.

  • IronPython is easy to embed in .NET applications as a scripting language

  • Easier to extend than CPython (C# is memory managed and C# types can be used directly in IronPython with no wrapping)

  • Silverlight!

A book on IronPython is now available via the Manning Early Access Program: IronPython in Action.

A useful resource for IronPython code examples, is the IronPython Cookbook.

A book that introduces core concepts of IronPython programming using a .NET–centric approach is Pro IronPython.

IronPython Winforms tutorial at ZetCode.

Other Python-Like Languages for .NET/Mono

Some other Python-like languages for .NET and Mono include:

Accessing .NET from CPython

Python for .NET is the reverse of IronPython, it lets you access .NET assemblies from CPython.


See also: PythonAndParrot, LoGix, IronPython IDE

IronPython (last edited 2022-09-25 12:38:41 by HuntBlanchat)

Unable to edit the page? See the FrontPage for instructions.