@@ -124,23 +124,22 @@ <h1>Python for .NET</h1>
124124 < td align ="left " valign ="top ">
125125 < p > Python for .NET is a package that gives Python programmers
126126 nearly seamless integration with the .NET Common Language Runtime
127- (CLR) and provides a powerful application scripting tool for .NET
127+ (CLR) and Mono and provides a powerful application scripting tool for .NET
128128 developers. Using this package you can script .NET applications or
129129 build entire applications in Python, using .NET services and
130- components written in any language that targets the CLR (Managed
131- C++, C#, VB, JScript).
130+ components written in any language that targets the CLR (C#, VB.NET, F#, C++/CLI).
132131 </ p >
133132 < p > Note that this package does < em > not</ em > implement Python as a
134133 first-class CLR language - it does not produce managed code (IL)
135- from Python code. Rather, it is an integration of the C Python
136- engine with the .NET runtime. This approach allows you to use use
137- CLR services and continue to use existing Python code and C-based
134+ from Python code. Rather, it is an integration of the CPython
135+ engine with the .NET or Mono runtime. This approach allows you to use use
136+ CLR services and continue to use existing Python code and C-API
138137 extensions while maintaining native execution speeds for Python
139138 code. If you are interested in a pure managed-code implementation
140139 of the Python language, you should check out the < a href ="http://www.ironpython.com "> IronPython</ a >
141140 project, which is in active development.
142141 </ p >
143- < p > Python for .NET is currently compatible with Python releases 2.3
142+ < p > Python for .NET is currently compatible with Python releases 2.6
144143 and greater. Current releases are available at the < a href ="http://pythonnet.github.io/ ">
145144 Python for .NET website </ a > . To subscribe to the < a href ="http://mail.python.org/mailman/listinfo/pythondotnet ">
146145 Python for .NET mailing list </ a > or read the < a href ="http://mail.python.org/pipermail/pythondotnet/ ">
@@ -164,17 +163,15 @@ <h2>Installation</h2>
164163 to have installed Python on your machine before using the source
165164 release.
166165 </ p >
167- < p > < strong > Running on Linux/Mono:</ strong > preliminary testing
166+ < p > < strong > Running on Linux/Mono:</ strong > Unit testing
168167 shows that PythonNet will run under < a href ="http://www.go-mono.com "> Mono</ a > ,
169- though the Mono runtime is not yet complete so there still may be
170- problems. The Python for .NET integration layer is 100% managed
171- code, so there should be no long-term issues under Mono - it
172- should work better and better as the Mono platform matures.
168+ though the Mono runtime is less supported so there still may be
169+ problems.
173170 </ p >
174171 < p > Note that if you are running under Mono on a *nix system, you
175172 will need to have a compatible version of Python installed. You
176173 will also need to create a symbolic link to the copy of
177- libpython2 .x.so (in your existing Python installation) in the
174+ libpython[v] .x.so (in your existing Python installation) in the
178175 PythonNet directory. This is needed to ensure that the mono
179176 interop dll loader will find it by name. For example:
180177 </ p >
@@ -186,7 +183,7 @@ <h2>Getting Started</h2>
186183 "work just the way you'd expect in Python", except for cases that
187184 are .NET specific (in which case the goal is to work "just the way
188185 you'd expect in C#"). In addition, with the IronPython project
189- gaining traction , it is my goal that code written for IronPython
186+ having established a community , it is my goal that code written for IronPython
190187 run without modification under Python for .NET.
191188 </ p >
192189 < p > If you already know Python, you can probably finish this readme
0 commit comments