Hi Brian, I must say that Python.NET feels like an approach I would use more than IronPython. I like being able to mix both C extensions and .NET extensions together. I haven't had a need for .NET functionality yet, but if I do it will have to be Python.NET because the rest of my code makes extensive use of ctypes. Thanks Mark -----Original Message----- From: pythondotnet-bounces+mark.mcmahon=autodesk.com@python.org [mailto:pythondotnet-bounces+mark.mcmahon=autodesk.com@python.org] On Behalf Of Brian Lloyd Sent: Wednesday, January 25, 2006 11:11 AM To: f.geiger@vol.at; pythondotnet@python.org Subject: Re: [Python.NET] Any plans for supporting CLR2.0?

Dear all,

I'd like to integrate CPython- and Boo-programs. As I am already on CLR2.0 I wonder when Python for .NET could be available for CLR2.0. As its install file suggests it is ready for CLR1.1 only, right?

Kind regards Franz GEIGER

The pre-built versions I post are currently built for 1.1, but you should be able to build it against 2.x with minimal pain (though it wont support 2.x-only features, of course). Michael Eddington posted a build against 2.0 back in October: http://mail.python.org/pipermail/pythondotnet/2005-October/000406.html I hope to get some time starting in Feb. to work on some bugs that have been reported and implement support for generics, etc. I've been slacking off a bit lately given that IronPython really seems to be taking off, but it seems like it would still be useful to have a native bridge with support for at least the bigger changes in CLR 2.x. Brian Lloyd brian@zope.com V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com _________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet