Ironpython book?

[Fredrik Lundh]

AFAIK, it's a long-completed research project. I do not know of anybody
planning to fork it to a new project, though that of course does not
rule out that somebody might be planning to do so.

brian's latest development blog entry is from april 13th, this year.

http://brianlloyd.blogspot.com/

"I'm happy to say its been a pretty busy month in Python
for .NET-land"

</F>

 

[Alex Martelli]

But is IronPython sort of the 'official' .NET implementation of Python
though? I know there is a difference between the two, but I haven't
heard about Python.NET in so long that I thought maybe it wasn't being
developed/used anymore. IronPython seems to be the equivalent of Jython
for .NET.

Sure, particularly since both Jython and IronPython are brainchildren of
Jim Hugunin. But, apparently, we're having communication problems.
Since I say that Python.NET is "a long-completed research project", what
contradition do you find between that and your opinion that "it [isn't]
being developed/used anymore"? Why should a research project, that was
finished years ago and to which (to the best of my knowledge) no
followup is planned, be "developed" any further?

IOW, although I believe it's absurd to call a research project "dead"
when it's completed, I know of no current nor planned development for
Python.NET.


Alex

 

[John Salerno]

Jim Hugunin. But, apparently, we're having communication problems.
Since I say that Python.NET is "a long-completed research project", what
contradition do you find between that and your opinion that "it [isn't]
being developed/used anymore"? Why should a research project, that was
finished years ago and to which (to the best of my knowledge) no
followup is planned, be "developed" any further?

I was just saying what my thoughts were before you told me that it was a
completed project. What I had thought was that work on it had stopped
and it wasn't being used anymore, perhaps because IronPython was
becoming the main .NET implementation to use.

But it sounds like, from Fred's post, that work is still being done on
it. My main point in asking was just that I hadn't heard as much about
it as IronPython lately, and I was just curious what the community would
think about two competing .NET implementations, since a big part of
Python is having one main way to do everything (I think).

 

[John Salerno]

But it sounds like, from Fred's post

"Fredrik". Have no idea why Fred slipped out.

 

[Fredrik Lundh]

But it sounds like, from Fred's post, that work is still being done on
it. My main point in asking was just that I hadn't heard as much about
it as IronPython lately, and I was just curious what the community would
think about two competing .NET implementations, since a big part of
Python is having one main way to do everything (I think).

are we talking about two different things here, perhaps ?

the "Python for .Net" tool I'm talking about is an integration tool that
lets you use CPython and CPython extensions together with CLR stuff,
while IronPython is a pure-CLR implementation of Python.

there was also, once upon a time, an experimental Python compiler for
the .Net platform:

http://starship.python.net/~skippy/dotnet/index.html

but that project was abandoned years ago.

</F>

 

[John Salerno]

are we talking about two different things here, perhaps ?

the "Python for .Net" tool I'm talking about is an integration tool that
lets you use CPython and CPython extensions together with CLR stuff,
while IronPython is a pure-CLR implementation of Python.

Yes, I'm referring to Python for .NET. I might be wrong to call it
Python.NET, but I thought I had seen that name as well (unless it really
*is* something different). And the difference between the it and
IronPython, as I understood it, is the same as you described above, so
I'm sure we are talking about the same thing.

Sorry for being so confusing!

 

[Taylor Boon]

brian's latest development blog entry is from april 13th, this year.

http://brianlloyd.blogspot.com/

"I'm happy to say its been a pretty busy month in Python
for .NET-land"

</F>

Project page is at

http://sourceforge.net/projects/pythonnet

Brian and co. are in the process of putting together a 2.0 release that will
work with .NET 2.0. Works with mono too, for all those "decent hacker" types
out there...

BTW, IronPython compiles Python code into CLR byte codes; Python.NET allows
CPython code to call into managed code libraries and services.

Cheers,
Taylor

 

[Alex Martelli]

Yes, I'm referring to Python for .NET. I might be wrong to call it
Python.NET, but I thought I had seen that name as well (unless it really
*is* something different). And the difference between the it and
IronPython, as I understood it, is the same as you described above, so
I'm sure we are talking about the same thing.

Sorry for being so confusing!

Oh, OK -- I thought you DID refer to the old research project!!!

Yeah, the terms "Python.NET" and "Python _for_ .NET" have sometimes been
used interchangeably in the past, that's true. Confusing...!


Alex

 

[John Salerno]

Oh, OK -- I thought you DID refer to the old research project!!!

Yeah, the terms "Python.NET" and "Python _for_ .NET" have sometimes been
used interchangeably in the past, that's true. Confusing...!

Heh heh, well it's still my fault for not knowing what I'm talking about!