Steve Dower added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19351> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
