[IronPython] Default install location and site-packages
brian.curtin at gmail.com
Tue Oct 6 06:43:02 PDT 2009
On Tue, Oct 6, 2009 at 06:45, Michael Foord <fuzzyman at voidspace.org.uk>wrote:
> Hello guys,
> The msi installer installs by default into "C:\Program Files\IronPython
> 2.6". It also creates a "Lib\site-packages" folder.
> Presumably the intention is that site-packages is for installed modules /
> packages, however "Program Files" is a special location and normal users
> (Vista / Windows 7) *can't* create files there. This means that distutils
> *must* be run with elevated permissions to install into this location.
> It doesn't work anyway because distutils attempts to bytecode-compile,
> which unsurprisingly fails with IronPython - but that bug in distutils will
> be fixed shortly.
> I don't have an obvious solution (per user site-packages perhaps?) but
> present the problem. Python circumvents this problem by *not* installing
> into "Program Files".
> All the best,
FWIW, the first time I installed IronPython via MSI I just clicked through
the installer without looking and was surprised to see that it went to
Program Files (user error, I know). I actually had to do a file search to
find it because, out of habit, I was expecting it at C:\IronPython.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users