Opened at 2011-01-12T07:20:34Z
Last modified at 2016-03-22T05:02:52Z
#1302 closed defect
installing Python 3 breaks bin\tahoe on Windows — at Initial Version
| Reported by: | davidsarah | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | 1.12.0 |
| Component: | packaging | Version: | 1.8.1 |
| Keywords: | windows regression setuptools python | Cc: | |
| Launchpad Bug: |
Description
Installing native-Windows Python 3 breaks bin\tahoe, because it changes the registry association for 'Python.File' to the Python 3 interpreter. This results in syntax errors because tahoe.pyscript is not compatible with Python 3.
(The exact version/installer I used was "Windows x86 MSI Installer (3.2b2)" from http://www.python.org/download/releases/3.2/ .)
This is strictly speaking a bug in zetuptoolz, but only Tahoe uses zetuptoolz.
Workarounds:
- bin/tahoe from a Cygwin prompt still works, because that uses the shebang line which is correct.
- c:\python26\python bin\tahoe (or whatever the full path to Python 2.x is) works.
- python bin\tahoe works if Python 2.x is on the PATH. The Python 3 installer does not change the PATH (either for the current user or the system-wide one).
Although building Tahoe-LAFS causes .pyscript to be associated with Python.File, it does not change the association for Python.File (intentionally, because that would be impolite!), so rerunning a build, install, or python setup.py scriptsetup does not fix the problem.
