Windows registry keys for Python file associations may have broken permissions, preventing build or installation

[davidsarah]

A build or install may fail on some Windows systems with the following error:

Setting up environment to run scripts for the current user...
error: Setup script exited with error: I was going to associate the
filetype .pyscript with Python.File for the current user, but that
won't work because the Python.File class does not exist in the
registry, as far as I can tell.
WindowsError(5, 'Access is denied')

See ​this tahoe-dev thread. The Windows system in that case was Windows 7 ultimate 64-bit.

This problem may occur because the Python.File key is not inheriting permissions from its parent (at least, clearing this permission inheritance is necessary to reproduce the problem on my machine).

For other reasons as well (#1302), we should probably stop relying on Python.File to point to the Python interpreter.

[daira]

When we remove zetuptoolz and switch to newer setuptools, this will be fixed because the scriptsetup code will go away. (Newer setuptools generates a Windows executable, and if this causes any regressions then we'll try to fix them upstream.)