Issue 757542: Need to register PythonLauncher as handler for .py (original) (raw)
Issue757542
Created on 2003-06-19 21:53 by jackjansen, last changed 2022-04-10 16:09 by admin. This issue is now closed.
| Messages (3) | ||
|---|---|---|
| msg16535 - (view) | Author: Jack Jansen (jackjansen) *  |
Date: 2003-06-19 21:53 |
| We still need a way to register PythonLauncher as the handler for .py, pyw and .pyc documents. PythonLauncher itself could do this easily, but that requires people to run PythonLauncher at least once. Or we would have to arrange for the installer to do it, or (at the very least) the IDE. The latter is difficult because we don't have access to the Launch Services API from Python, yet. | ||
| msg16536 - (view) | Author: Jack Jansen (jackjansen) * |
Date: 2003-06-20 21:22 |
| Logged In: YES user_id=45365 Turns out there isn't an API for setting the handler, at least not a public one. But PythonLauncher now does test that it is the current handler, and shows a (supressible) warning dialog if it isn't. I hope the magic of the installer, combined with the fact that PythonLancher advertises itself as being able to handle Python documents, will do the trick. I'm leaving this report open until that has been confirmed, though. | ||
| msg16537 - (view) | Author: Jack Jansen (jackjansen) * |
Date: 2003-06-28 20:30 |
| Logged In: YES user_id=45365 Pascal Oberndoerfer tested the new installer on a fresh machine, and everything appears to be okay. By default the IDE opens python scripts, and PythonLauncher is the second choice. When PythonLauncher is run it will also show a (suppressible) warning if it isn't the current handler. That's good enough for me. |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:09:21 | admin | set | github: 38685 |
| 2003-06-19 21:53:27 | jackjansen | create |