[IronPython] Default install location and site-packages

[Curt Hagenlocher]

In principle, allowing unprivileged users to install code into a location
where it can unknowingly be accessed by privileged users is a security
problem. A "per-user" approach is the right one.

On Tue, Oct 6, 2009 at 4:45 AM, 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,
>
> Michael
>
> --
> http://www.ironpythoninaction.com/
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20091006/ea0b7541/attachment.html>