[IronPython] IronPython Post 2.0 Roadmap

Harry Pierson Harry.Pierson at microsoft.com
Sat Jul 19 18:34:51 CEST 2008

Hosting features are all done via the DLR, so that's a separate team. As for "ability to interact with the rest of the .Net framework", can you be more specific about what you're looking for in that space? What *isn't* IPy doing that you want it to?

Harry Pierson
Senior Program Mangager, IronPython
Visual Studio Managed Languages

email  : harry.pierson at microsoft.com<mailto:harry.pierson at microsoft.com>
office : 425/705-6045
mobile : 425/761-0293
weblog : http://devhawk.net<http://devhawk.net/>

"Don't worry about people stealing your ideas.
  If your ideas are any good,
  you'll have to ram them down people's throats."
          - Howard Aiken<http://en.wikipedia.org/wiki/Howard_Aiken>

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dody Gunawinata
Sent: Saturday, July 19, 2008 12:56 AM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython Post 2.0 Roadmap

For me, the main strength of IronPython is its hosting API and the simplicity of the Python language. It's pretty amazing on what combination of C# and IronPython hosting API can do - we use it from running business rules table, sending python command in a game project and powering our CMS. In our next business project, we are planning to expose a bunch of IronPython scripts to the administrator role. Yeah, it's a poor man's DSL, but it's already there and you dont' have to spend time writing all the crufts required to write a DSL.

So I'd much prefer a much stronger features in the hosting and ability to interact with the rest of the .Net framework than supporting a new version of the Python language.

Dody G.
On Sat, Jul 19, 2008 at 8:54 AM, Dan Eloff <dan.eloff at gmail.com<mailto:dan.eloff at gmail.com>> wrote:
> There is a fair possibility that the 'community' will prefer Python 2 for
> several years (3-4 guesstimate).
> Michael
I would guess it will take less time for IronPython, because most of
the libraries don't work in ipy anyway. There's fewer things to hold
you back at the 2 level. If IronPython 3 were out right now, I'd use
it. If CPython 3 were out right now, I wouldn't.

Users mailing list
Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20080719/ec36cd8c/attachment.html>

More information about the Ironpython-users mailing list