Need to register PythonLauncher as handler for .py

[jackjansen]

BPO	757542
Nosy	@jackjansen

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/jackjansen'
closed_at = <Date 2003-06-28.20:30:48.000>
created_at = <Date 2003-06-19.21:53:27.000>
labels = ['OS-mac']
title = 'Need to register PythonLauncher as handler for .py'
updated_at = <Date 2003-06-28.20:30:48.000>
user = 'https://github.com/jackjansen'

bugs.python.org fields:

activity = <Date 2003-06-28.20:30:48.000>
actor = 'jackjansen'
assignee = 'jackjansen'
closed = True
closed_date = None
closer = None
components = ['macOS']
creation = <Date 2003-06-19.21:53:27.000>
creator = 'jackjansen'
dependencies = []
files = []
hgrepos = []
issue_num = 757542
keywords = []
message_count = 3.0
messages = ['16535', '16536', '16537']
nosy_count = 1.0
nosy_names = ['jackjansen']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue757542'
versions = []

[jackjansen]

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.

[jackjansen]

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.

[jackjansen]

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.