Hi Martin/Jim, > it would be interesting to hear feedback as to how important having > a version if IronPython running on .Net 1.1 is for you.
Really, Really important !!!!! :-) I'm a total CPython convert having been a Python developer for the last 1 1/2 years, but just took a .NET role. I'd love to convince my organisation of the power of Python, but I'm going to need to show them what it can do. They've shelled out for VS.NET 2003 (v1.1) recently and aren't likely to fork out for VS 2005 (v2.0) even when it's released - they are still running W2K on the desktop too!. I can't believe this is a unique situation. Out here beyond the walls of the Redmond Campus, we don't all queue up to buy the latest as soon as it is released ;-), much less large organisations trying to leverage the most value from substantial existing investment in software. Of course I could develop with the SDK without Visual Studio, but in reality I would have thought that in a large number of organisations that's not going to happen either. Finally, on a personal level I have a licensed copy of VS 2003 at home, and again can't justify the cost of VS 2005 when it comes out. (Wife and two kids to support, sob, sob ;-) So IronPython (albeit with reduced features/functionality) under .Net v1.1: please, please, pretty please !!! Paul Sweeney --- [This E-mail was scanned for viruses for your protection] _______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
