Editing IronPython (section)

=== Differences with CPython ===
{{expand section|date=July 2012}}
There are some differences between the Python reference implementation CPython and IronPython.<ref name="compcpython">{{cite web
| url=http://www.codeplex.com/IronPython/Wiki/View.aspx?title=Differences&referringTitle=Home
| title=Differences between IronPython 1.0 and CPython 2.4.3
|publisher=[[Microsoft]]
| date=2007-12-18
| access-date=2008-02-09}}</ref> Some projects built on top of IronPython are known not to work under CPython.<ref>{{cite web
| url=http://lists.ironpython.com/pipermail/users-ironpython.com/2008-January/006297.html
| title=New Project: Implementing .NET Libraries in Pure Python
| last=Foord
| first=Michael
| access-date=2008-02-09
| archive-url=https://web.archive.org/web/20080830011024/http://lists.ironpython.com/pipermail/users-ironpython.com/2008-January/006297.html
| archive-date=2008-08-30
| url-status=dead
}}</ref> Conversely, CPython applications that depend on extensions to the language that are implemented in C are not compatible with IronPython
,<ref>{{cite web
| url=http://dirtsimple.org/2005/10/children-of-lesser-python.html
| title=Children of a Lesser Python
| last=Eby |first=Phillip
| date=15 October 2005
| access-date=2008-07-09}}</ref> unless they are implemented in a .NET interop. For example, [[NumPy]] was wrapped by Microsoft in 2011, allowing code and libraries dependent on it to be run directly from .NET Framework.<ref>{{cite web | url=https://www.infoq.com/news/2011/07/NumPy-NET | title=NumPy and SciPy for .NET | access-date=2019-04-05}}</ref>