My first reaction to "python.net.exe" is that nearly everyone would end up wrapping it in a script: it's long and complex. IMHO, people like short names, particularly if they follow a pre-established pattern (eg, csc, fsc, plc, cc, etc).
My second is that "should not" and "will not" depend entirely on copyright issues at worst, and association at best. "Python.NET" and "Python for .NET" -- who's going to come into the community and be able to tell the difference? There's also http://www.zope.org/Members/Brian/PythonNet/, which Brian could tell you about. I think the name should be unique -- and short. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Tarlano Sent: Thursday, April 14, 2005 12:29 PM To: Muhammad Abubakar; Discussion of IronPython Subject: Re: [IronPython] To Compile or Not to compile, that's the question I still think the name python.net (i.e. python.net.exe) has not been taken. ActiveState's 2001 python for .net, http://www.activestate.com/Corporate/Initiatives/NET/Research.html, should not preempt the use of the name, since they surely aren't doing anything with it and only used the name for the zip not the name of the project. _______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
