[issue25125] "Edit with IDLE" does not work for shortcuts

Terry J. Reedy added the comment: This is not an IDLE code issue, but an installation issue, and I think one main entry with a submenu is proper. I just tried clicking on '3.5.3' and '3.6.2' and both opened an editor for a .py file with the corresponding version. -- resolution: ->

[issue25125] "Edit with IDLE" does not work for shortcuts

Steve Dower added the comment: Because of the way Open With works, we can't do this unless we start building an EXE to launch IDLE (Windows automatically picks up most of the details from the target executable, so it will show as "pythonw" if we do it without the launcher). Unassigning

[issue25125] "Edit with IDLE" does not work for shortcuts

Terry J. Reedy added the comment: Putting them under the current 'Open with >' would also be alright. (It currently lists Notepad, Wordpad, and Py launcher for Windows (console), which I presume means run with default for Py. What I was requesting is that the version be included with the

[issue25125] "Edit with IDLE" does not work for shortcuts

Thijs van Dien added the comment: Terry, I'll write here not to open the old ticket (yet). I'd argue listing all IDLE's under "Open with" is still the best option, rather than yet another menu option. First of all, there is nothing conceptually different about opening the file with IDLE vs.

[issue25125] "Edit with IDLE" does not work for shortcuts

Terry J. Reedy added the comment: In #23546, I requested a separate 'Edit with IDLE x.y' (I mis-said 'Open') on the context menu for each installed version. I said I would be OK with one 'Edit with IDLE' entry and a submenu, as proposed by someone else. I agree that this will be better in

[issue25125] "Edit with IDLE" does not work for shortcuts

Steve Dower added the comment: Terry (nosied) made the request for the context menu in issue 23546, so if you want it removed you'll need to convince him. Personally I prefer the context menu, but I typically replace the default file association with one that's better for me anyway so I'm not

[issue25125] "Edit with IDLE" does not work for shortcuts

Thijs van Dien added the comment: If this turns out to be a Windows problem, I'd insist not to close it as such but to find away around that. After all, in Python 3.4 there was no subcommand, and all was fine. Do we really need that second level menu? I found it to be less user-friendly as

[issue25125] "Edit with IDLE" does not work for shortcuts

eryksun added the comment: > I don't believe %1 is necessarily correct here either, but maybe > with %* it's redundant anyway %0, %1, or %L is lpFile. On older systems "%L" guarantees using the long filename, but this is pointless nowadays. %* (i.e. %2 through %9) is lpParameters, which is

[issue25125] "Edit with IDLE" does not work for shortcuts

Steve Dower added the comment: Creating a "dumb" item was discussed and rejected. I don't see how passing the subkey is an issue if it works. The name of the verb is considered public API surface, so we can't easily change it anyway. What may be the issue is the use of "%L", which I recall

[issue25125] "Edit with IDLE" does not work for shortcuts

eryksun added the comment: > Does notepad handle clicking "edit" on a shortcut to a batch file? > Maybe subcommands don't have exactly the same semantics as regular > verbs... In Windows 7 SP1 a regular verb works fine from a shortcut, but apparently not a subcommand. OTOH, Windows 10 seems

[issue25125] "Edit with IDLE" does not work for shortcuts

Steve Dower added the comment: Does notepad handle clicking "edit" on a shortcut to a batch file? Maybe subcommands don't have exactly the same semantics as regular verbs... -- ___ Python tracker

[issue25125] "Edit with IDLE" does not work for shortcuts

Steve Dower added the comment: Ah, I misread that part. Will have to look deeper, but I'm not actually sure that shortcuts are supposed to support the same operations (though if it shows up, I guess it should work). -- ___ Python tracker

[issue25125] "Edit with IDLE" does not work for shortcuts

eryksun added the comment: > Ah, I misread that part. Will have to look deeper, but I'm not > actually sure that shortcuts are supposed to support the same > operations (though if it shows up, I guess it should work). A LNK shortcut should support the same commands (e.g. open, edit) as its

[issue25125] "Edit with IDLE" does not work for shortcuts

Thijs van Dien added the comment: That works fine, but then again the ticket only concerns the context menu of _shortcuts_ to Python files. Opening Python files directly, either via "Edit with IDLE" in context menu or directly via the CLI, has worked from the beginning. --

[issue25125] "Edit with IDLE" does not work for shortcuts

Changes by Steve Dower : -- assignee: -> steve.dower ___ Python tracker ___ ___

[issue25125] "Edit with IDLE" does not work for shortcuts

Steve Dower added the comment: Can you try executing the following command (fix the paths as necessary, but leave all the quotes where they are): "C:\Program Files (x86)\Python 3.5\python.exe" -m idlelib "C:\test.py" That's what should be launched by the menu, with a minor change to use

[issue25125] "Edit with IDLE" does not work for shortcuts

New submission from Thijs van Dien: Right clicking a Python file shows "Edit with IDLE" in the context menu, then offering a next menu where one can choose which particular version of IDLE should be used. This works fine. Whenever a shortcut is created to a Python file, the same context menu