When I say CPython 2.5 compatibility I really just mean Python 2.5 compatibility. When speaking of multiple Python implementations CPython is just what everyone calls the original implementation of Python which is written in C that all the alternate implementations track.
The goal for the DLR is to get great cross-language interop between the dynamic languages, not the ability to use Python objects from C#. But this is possible to a certain extent already via interfaces or common base classes. The most important missing feature is you can't do new SomePythonType() and that won't change in IronPython 2.0 / DLR 1.0. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pigneri, Rocco Sent: Tuesday, January 15, 2008 11:31 AM To: Discussion of IronPython Subject: Re: [IronPython] Roadmap for IronPython 2.0 Dino, Thank you for your response. Funny that I would check my e-mail seconds before this message hit my mail box :-). We don't really have a document like this but the general goal is to ship IronPython 2.0 by the end of the year. The goals for IronPython generally include CPython 2.5 compatibility and fully running on top of the DLR. And of course we've already seen numerous improvements from IronPython 1.1 -> 2.0 and I expect to see a bunch more random improvements as we continue (e.g. bug fixes, performance, etc...). Excuse my ignorance--again, I am new to Python--but why is it important to have CPython 2.5 compatibility as opposed to, say, Python 2.5 compatibility? Or are the two identical from a "user" perspective? For the DLR its self the plan is to ship a v1.0 around the same time as IronPython 2.0. The goal for DLR v1.0 is to get great hosting support so that apps can consume multiple languages and languages can plug into the DLR and run inside of applications in a reasonable manner. When you say this, do you mean that this will allow for situations such as letting C# instantiate a type that defined in IronPython and then manipulate this object? This would be useful in a situation where you have a unit testing framework written in a static language (like NUnit) or an analysis tool that expects to consume a static language. Or is the goal more to ensure that different dynamic languages can talk to each other (such as Python and Ruby) across assembly boundaries? Thank you, Rocco ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dino Viehland Sent: Tuesday, January 15, 2008 2:16 PM To: Discussion of IronPython Subject: Re: [IronPython] Roadmap for IronPython 2.0 We don't really have a document like this but the general goal is to ship IronPython 2.0 by the end of the year. The goals for IronPython generally include CPython 2.5 compatibility and fully running on top of the DLR. And of course we've already seen numerous improvements from IronPython 1.1 -> 2.0 and I expect to see a bunch more random improvements as we continue (e.g. bug fixes, performance, etc...). For the DLR its self the plan is to ship a v1.0 around the same time as IronPython 2.0. The goal for DLR v1.0 is to get great hosting support so that apps can consume multiple languages and languages can plug into the DLR and run inside of applications in a reasonable manner. The really interesting question at this point for DLR v1.0 is how finalized the language implementer API will be. We still have some work to know if that'll be finalized in time or if we'll be expecting some breaking changes in that area post DLR 1.0. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pigneri, Rocco Sent: Tuesday, January 15, 2008 8:09 AM To: [email protected] Subject: [IronPython] Roadmap for IronPython 2.0 Dear all, I am new to IronPython. IP 1.1 looks really great, and I have really enjoyed learning to use it over the last few weeks. I'm impressed with both its power and ease of use. One thing that I would love to learn more about, however, is the planned features and goals for 2.0, particularly with regard to the DLR, but I haven't been able to find a feature roadmap or anything like that yet. I have looked at the release notes and the documentation download for IP 2.0 itself, but those documents were either very specific to each release or focused on documenting the code of the interpreter rather than the features/goals of 2.0. Would someone be able to point me towards that document? Thank you, Rocco Pigneri
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
