Opened at 2011-02-25T00:44:15Z
Last modified at 2016-03-22T05:02:52Z
#1371 closed defect
Windows registry keys for Python file associations may have broken permissions, preventing installation — at Initial Version
Reported by: | davidsarah | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | 1.12.0 |
Component: | packaging | Version: | 1.8.2 |
Keywords: | windows setuptools | Cc: | |
Launchpad Bug: |
Description
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.
Note: See
TracTickets for help on using
tickets.