Closed Bug 623980 Opened 14 years ago Closed 12 years ago

SDK: bin\activate.bat doesn't find python, but it is installed

Categories

(Add-on SDK Graveyard :: General, defect, P2)

x86
Windows XP
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aryx, Unassigned)

Details

After installing the add-on SDK 1.0b1, I read the readme and wanted to run it on Windows XP SP 3 32-bit. Python 2.6.5, 2.7.1, 3.1.3 are installed.

After switching to the add-on SDK directory, running bin\activate.bat like described in the README throws an error in German:

Fehler: Der angegebene Registrierungsschlüssel oder Wert konnte nicht gefunden werden.
Der Befehl "python" ist entweder falsch geschrieben oder konnte nicht gefunden werden.

Translated:
"Error: The given registry key or value could not be found.
The command "python" is either written wrong or could not be found."

HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.6\InstallPath exists and the value is F:\Software\Programmierung\Python\Python26\
If you enter "PATH" (without the quotes) in a command prompt, what exactly is listed?
PATH=F:\Software\Programmierung\Editoren\Komodo Edit\;F:\Software\Programmierung
\TeX\MiKTeX\miktex/bin;C:\Programme\REALTEK Semiconductor Corp.\Realtek Fast Eth
ernet Adapter Driver;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\
Programme\ATI Technologies\ATI Control Panel;C:\Programme\Gemeinsame Dateien\Tel
eca Shared;C:\Programme\Intuwave\Shared\mRouterRuntime;C:\WINDOWS\system32\Windo
wsPowerShell\v1.0;F:\Software\Basis\GTK\bin

(I dropped Python 2.6 since filing this bug but still have 2.7 installed).

Python is not added automatically to the PATH variable, see http://docs.python.org/using/windows.html#finding-the-python-executable
I don't believe Python 3.1 is supported yet.

I normally just start up a console using the shortcuts that mozillabuild ( https://developer.mozilla.org/en/Windows_Build_Prerequisites#MozillaBuild ) creates, and then everything seems to work alright.

Not really a "solution", but would probably work as a workaround, if uninstalling Python 3.1 doesn't work.
Can you please at it to readme file? As Python 2.7.1 doesn't seem to act different than 2.6 and the problem also happened with 2.6 when I reported the bug, it doesn't depend on the Python version.
Priority: -- → P2
Target Milestone: --- → 1.0
(automatic reprioritization of 1.0 bugs)
Priority: P2 → P1
Target Milestone: 1.0 → 1.1
Assignee: nobody → myk
Priority: P1 → P2
Target Milestone: 1.1 → 1.2
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.2 → ---
Unassigning myself from bugs I am not actively working on.
Assignee: myk → nobody
I suspect this has been fixed by way of bug 700388.
aryx: can you reproduce the problem with the latest version of the SDK?
It's fixed with SDK 1.4.3
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [triage:followup]
You need to log in before you can comment on or make changes to this bug.