SynonymsBot
Synonyms for ironpython or Related words with ironpython
ironruby
haxe
jython
jruby
cpython
wxwidgets
powerbuilder
beanshell
applescript
clojure
autoit
ocaml
winrt
msvc
freebasic
mingw
codeigniter
msxml
msbuild
rebol
cakephp
realbasic
rexx
xcode
netbeans
wxpython
xunit
textmate
monodevelop
visualage
hypertalk
xulrunner
symfony
codelite
pyqt
clang
angularjs
autolisp
gedit
zend
mediawiki
coffeescript
xamarin
freepascal
cython
libwww
cmake
powershell
rubymotion
kixtart
Examples of "ironpython"
web2py code can run with
IronPython
on .NET. Limitations:
There are some differences between the Python reference implementation CPython and
IronPython
. Some projects built on top of
IronPython
are known not to work under CPython. Conversely, CPython applications that depend on extensions to the language that are implemented in C (e.g. NumPy) are not compatible with
IronPython
.
The performance characteristics of
IronPython
compared to CPython, the reference implementation of Python, depends on the exact benchmark used.
IronPython
performs worse than CPython on most benchmarks taken with the PyStone script but better on other benchmarks.
In October 2010, after Microsoft abandoned the
IronPython
project, Hugunin left Microsoft to work for Google.
The DLR is used to implement dynamic languages on the .NET Framework, specifically by
IronPython
and IronRuby projects.
can also be used on Linux systems by compiling it under Mono, which supports C# and
IronPython
.
IronPython
is supported on Silverlight. It can be used as a scripting engine in the browser just like the JavaScript engine.
IronPython
scripts are passed like simple client-side JavaScript scripts in codice_1-tags. It is then also possible to modify embedded XAML markup.
IronPython
makes extensive use of reflection. When passed in a reference to a .NET object, it will automatically import the types and methods available to that object. This results in a highly intuitive experience when working with .NET objects from within an
IronPython
script.
Jim Hugunin is a software programmer who created the Python programming language extension Numeric (ancestor to NumPy), and later created Python implementations for the Java Platform (Jython) and for Microsoft .NET platform (
IronPython
); he has also co-designed the AspectJ extension for the Java programming language. He worked for Microsoft from 2004 to 2010, mainly on
IronPython
and Dynamic Language Runtime.
SharpDevelop integrates Graphic User Interface Designers for the C#, VB.NET, Boo, and the
IronPython
and IronRuby languages, using the following GUI technologies:
Free tools (Visual Studio Express in combination with the Robotics Developer Studio) enable programming the NXT using the C# language. Other supported languages include
IronPython
and VB.NET.
programs coded in any language supported on .NET on Windows, such as C#, C++/CLI, F#,
IronPython
and IronRuby. The system
The DLR services are currently used in the development version of IronRuby, a .NET implementation of the Ruby language, and for
IronPython
.
IronPython
may perform better in Python programs that use threads or multiple cores, as it has a JIT, and also because it doesn't have the Global Interpreter Lock.
IronPython
is written entirely in C#, although some of its code is automatically generated by a code generator written in Python.
Even though the library itself is written in C#, it may be used from any .NET compatible language and has samples of various usages including from
IronPython
scripting.
IronPython
is an implementation of the Python programming language targeting the .NET Framework and Mono. Jim Hugunin created the project and actively contributed to it up until Version 1.0 which was released on September 5, 2006. Thereafter, it was maintained by a small team at Microsoft until the 2.7 Beta 1 release; Microsoft abandoned
IronPython
(and its sister project IronRuby) in late 2010, after which Hugunin left to work at Google.
One of IronPython's key advantages is in its function as an extensibility layer to application frameworks written in a .NET language. It is relatively simple to integrate an
IronPython
interpreter into an existing .NET application framework. Once in place, downstream developers can use scripts written in
IronPython
that interact with .NET objects in the framework, thereby extending the functionality in the framework's interface, without having to change any of the framework's code base.
This feature takes advantage of the Dynamic Language Runtime (DLR) and has been designed specifically with the goal of interoping with dynamically typed languages like
IronPython
and IronRuby (Implementations of Python and Ruby for .NET).
JVM-based equivalents of these languages (Jython and JRuby) do not use global interpreter locks.
IronPython
and IronRuby are implemented on top of Microsoft's Dynamic Language Runtime and also avoid using a GIL.