<div dir="ltr"><div>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.</div>
<div> </div>
<div>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.</div>
<div> </div>
<div> </div>
<div>Dody G.<br><br></div>
<div class="gmail_quote">On Sat, Jul 19, 2008 at 8:54 AM, Dan Eloff <<a href="mailto:dan.eloff@gmail.com">dan.eloff@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">> There is a fair possibility that the 'community' will prefer Python 2 for<br>> several years (3-4 guesstimate).<br>><br>> Michael<br>><br><br></div>I would guess it will take less time for IronPython, because most of<br>
the libraries don't work in ipy anyway. There's fewer things to hold<br>you back at the 2 level. If IronPython 3 were out right now, I'd use<br>it. If CPython 3 were out right now, I wouldn't.<br><font color="#888888"><br>
-Dan<br></font>
<div>
<div></div>
<div class="Wj3C7c">_______________________________________________<br>Users mailing list<br><a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://nomadlife.org">nomadlife.org</a><br></div>