[IronPython] IronPython compilation with mono

Keith J. Farmer kfarmer at thuban.org
Tue Mar 29 20:20:21 CEST 2005

fepy -- OK?  fewer keystrokes, and google doesn't find "fepy.exe".  It also has that science geek charm.
ipy -- taken by spyware
ip -- taken by spyware
But then, I have some wonderfully long exe names here at work.
I'd also as soon keep versions seperate, rather than nested.  I've never considered a version number to be anything more than a label, since there isn't any universal way to distinguish the level of change from the version.  That is, version numbers increment in a rather arbitrary manner: might as well just give them unique distribution.  If the base libraries were stored in the GAC, one could use the standard config mechanisms for declaring which versions to use for side-by-side installations of IronPython.

From: users-ironpython.com-bounces at lists.ironpython.com on behalf of Jim Hugunin
Sent: Tue 3/29/2005 9:18 AM

I picked IronPythonConsole at the very start of the project knowing that
it would be so bad that I'd have to change it eventually.  As someone
else pointed out, ipython is already in use.  'ironpy' is the most
appealing of your list of options.  Does anyone have a better

Do you have a problem with the .exe at the end of the name or just the
length of IronPythonConsole?

The packaging is a good suggestion as well.  The tools that I use now to
extract zip files will be default put the files in a directory with the
name of the zip file, so the current design works fine on my box.  I
realize that isn't universal.  One dilemma with extracting into a
versioned directory is how often to change the name.  Do you think the
0.7.1 should go into the same directory as 0.7 or not?

More information about the Ironpython-users mailing list