[IronPython] To Compile or Not to compile, that's the question
mailinglist.account at gmail.com
Fri Apr 15 06:50:04 PDT 2005
All good points but,
I still don't see the problem, since you don't type the '.exe' part so
it is just 'python.net'
As for Brian's python for .NET, as good as I am sure it is, I really
have a hard time believing that any developer is going to have a hard
time telling the difference between IronPython and his..
On 4/14/05, Keith J. Farmer <kfarmer at thuban.org> wrote:
> 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
> I think the name should be unique -- and short.
> -----Original Message-----
> From: users-ironpython.com-bounces at lists.ironpython.com
> [mailto:users-ironpython.com-bounces at lists.ironpython.com] 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
> I still think the name python.net (i.e. python.net.exe) has not been
> ActiveState's 2001 python for .net,
> 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 at lists.ironpython.com
More information about the users-ironpython.com