Issue #3 resolved
Anonymous created an issue

I have python installed in C:\Program Files\Python27\python.exe, using the standard installer.

After installing with ALLUSERS=1, trying to start scripts explicitly with py.exe, failed, indicating the path C:\Program Files\Pthon27\python.exe did not exist (note the missing y).

After an uninstall of Python Launcher, the the old associations were not restored.

I tried again without ALLUSERS=1, but nothing changed.

Comments (6)

  1. Vinay Sajip

    Please can you tell me what is in the machine's registry under the following registry locations?

    HKEY_LOCAL_MACHINE\Software\Python\PythonCore HKEY_CURRENT_USER\Software\Python\PythonCore

    The launcher gets the values for where Python is installed from these registry locationa. Can you confirm whether the paths in these locations are correct?

    Also: which version of Windows was this machine running (including whether 32- or 64-bit)?

  2. Anonymous

    The second of these entries (HKCU) does not exist at all. I did the Python install for all users, so that probably makes sense.

    The first has no entries, just "folders", 2.4, 2.6 and 2.7.

    I have 32 bit WinXP.

    I will try and look at a different machine later today.

  3. Anonymous

    Another machine here looked very similar. I did not try installing Python Launcher there.

    HKLM\Software\Python\PythonCore\2.7\InstallPath is set correctly.

    One question. Does the installer even work without any version of Python 3 installed? I downloaded the source to the launcher, and tried running It won't run at all without some version of Python 3. Perhaps the rest of the installer is OK. I did not really look.

    I don't have Python 3 installed. Too much of my programming demands wxPython, which does not yet exist for that platform.

    I want the launcher so that I can have have the shortcuts to the various GUI programs I write us a pyw.exe and avoid opening a command window. Right now, making the shortcut say "c:\program files\python27\pythonw.exe" c:\myfiles\ works, but needs to be changed when updating Python.

    I could also name the main program prog.pyw, and launche it directly, but then I need to rename it back when debugging, when I want the output.

  4. Vinay Sajip

    Do you mean that on the first machine, InstallPath is correctly set? (I can't understand why just the "y" in "Python" would be missing, so I want to check if the source value could somehow be wrong.)

    Re. the need for Python 3 - that's only for running the tests. The launcher itself doesn't rely on any version of Python - it's a completely standalone C program.

    The association mechanism means that .pyw files will normally be launched by pyw.exe, which will in turn invoke pythonw.exe, and so will show no console. If you want to output diagnostics from these, I would suggest you try logging to a file rather than console output.

    You can use a customised command to execute any extension with pythonw.exe or python.exe, i.e. just depending on the shebang line rather than the extension.

  5. Anonymous

    Both machines had InstallPath correct. Specificially, nothing in regedit on either machine was mssing the y in Python. I did a search. I see nothing anywhere I can think of without the y.

    I was intending to use the associations that way. I would make the shortcut "c:\program files\python launcher\pyw.exe" c:\mydir\ when run "normally", and run from a command window during development. The files would NOT be named .pyw.

    My programs get changed very regularly, sometimes every few days. I need an easy way to see the normal errors that show up during development, such as misspelled identifiers.

  6. Log in to comment