Steve Dower added the comment: Ah, okay, so this is due to the embedded DLL in the installer that we extract and use to validate the install path (if you select a path that already exists, you get a prompt warning you).
I don't know why your %TEMP% directory was not read/write/execute, but since it works fine for most people I suspect a configuration issue on your machine. I have seen in the past some "security" policies that will break installers, though typically launching the installer from an elevated command prompt (one that says "Administrator: Command Prompt" in the title) typically avoids these issues. Glad you found a workaround at least. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22466> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
