Python for .NET preview 2 release

[Bryan]

"John J. Lee" <jjl at pobox.com> wrote in message news:87u18rx84u.fsf at pobox.com...
> "Bryan" <belred1 at yahoo.com> writes:
>
> > is this the same visual python .net that at activestate?  i didn't
> > know they python .net is still moving forward.  i also thought i
> > read somewhere that there were some limitations about using a
> > typeless language on the clr.  is this not true anymore?
>
> Visual Python is a plugin for the Visual Studio IDE, I believe.
>
> Python.NET was an implementation of Python directly on the CLR virtual
> machine.  It never got anywhere, and never will -- the CLR is hostile
> to languages like Python.
>
> I think Python for .NET is an interoperability framework -- I presume
> you can run CPython from .NET, and .NET from CPython, but it isn't
> Python *in* .NET.
>
> It would be nice if all this context were made clear on the Python for
> .NET page.
>
>
> John

but kobra is a way to scripts .NET services from python, and is supposedly very fast and efficient.  wasn't there a pycon speech
about this?   is this the same Python.NET that was referenced in that speech?

---

Reuse Mark Hammond's work on Python.NET - port python itself to the .NET.
Advantages

"Pure" .NET implementation
Other .NET modules can use Python based modules seamlessly
Easier to support complete .NET functionality
This would be a somewhat "brute force" approach - so perhaps better performing than other approaches. (unverified)

Disadvantages

a.       Poor performance (ref: Mark Hammond)
b.      Cannot easily access native python extensions
c.       A significant amount of work - again suitable for a more purist approach.

---

sorry, i was under the impression that all the different python .NET solutions were giving way to Kobra as being the best python
solution.  i thought the python community as a whole was going to rally around it.... i don't mean to take away anything from the
work and effort that has been done on Python.NET.  i was just surprised to see a new posting about other .NET solutions for python
continuing.

bryan