Opened at 2011-02-25T00:44:15Z

Closed at 2016-01-15T18:06:21Z

Last modified at 2016-03-22T05:02:52Z

#1371 closed defect (wontfix)

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

Reported by: davidsarah Owned by: davidsarah
Priority: major Milestone: 1.12.0
Component: packaging Version: 1.8.2
Keywords: windows setuptools Cc:
Launchpad Bug:

Description (last modified by daira)

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.

Change History (5)

comment:1 Changed at 2011-02-25T00:44:40Z by davidsarah

  • Owner changed from somebody to davidsarah
  • Status changed from new to assigned
  • Summary changed from Windows registry keys for Python file associations may have broken permissions, preventing installation to Windows registry keys for Python file associations may have broken permissions, preventing build or installation

comment:2 Changed at 2011-08-12T15:27:02Z by davidsarah

  • Milestone changed from undecided to 1.10.0

comment:3 Changed at 2016-01-15T18:06:21Z by daira

  • Description modified (diff)
  • Resolution set to wontfix
  • Status changed from assigned to closed

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.)

comment:4 Changed at 2016-01-15T19:10:14Z by daira

  • Milestone changed from soon to 1.11.0

comment:5 Changed at 2016-03-22T05:02:52Z by warner

  • Milestone changed from 1.11.0 to 1.12.0

Milestone renamed

Note: See TracTickets for help on using tickets.