➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Jason.Bray, loewis, steve.dower
Date 2014-06-13.20:25:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402691126.1.0.236319373235.issue19351@psf.upfronthosting.co.za>
In-reply-to
Content 
Okay, now it looks to me like the install that 'works' ran under the SYSTEM account while the one that didn't work ran under my (admin) user account.

This may be caused by running the installer from an elevated command prompt. If it detects that it needs to elevate, then it changes to SYSTEM, but if it detects that it doesn't, it will use the current account.

If you can run your install scripts as SYSTEM then I suspect it will work. I'm not yet clear on why it sometimes installs through the one account instead of the other.
History
Date User Action Args
2014-06-13 20:25:26steve.dowersetrecipients: + steve.dower, loewis, Jason.Bray
2014-06-13 20:25:26steve.dowersetmessageid: <1402691126.1.0.236319373235.issue19351@psf.upfronthosting.co.za>
2014-06-13 20:25:26steve.dowerlinkissue19351 messages
2014-06-13 20:25:25steve.dowercreate