[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Steve Dower added the comment: Hey Terry, as a first step towards fixing the current 3.5 issue of not having Edit with IDLE at all, is it okay if the "Edit with IDLE" menu launches (approx.) "py -m idlelib.idle %1"? Currently the shortcut menu is part of the launcher - the "Open" item launches

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Liam Marsh added the comment: >Why run a batch file instead of directly running the .pyw script via >>pythonw.exe? A batch file is executed by cmd.exe, which is a console >>application. the strange thing is that it exists -- ___ Python tracker

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Steve Dower added the comment: Setting up a progid is my intent, but it will be linked very closely to the executable. Currently it will show up as "pythonw.exe" and not idle. I didn't try with the batch file, but I'm fairly sure that's failed in the past too. I like the idea of (approximately

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

eryksun added the comment: > the windows packages already include an "idle.bat" launcher next > to the "idle.py" and "idle.pyw" files. However, this launcher > is (strangely enough) not used in the "edit with idle" command. Why run a batch file instead of directly running the .pyw script via

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

eryksun added the comment: > I'd prefer to be able to list them all under the Open With menu, > since that also allows users to easily make any of them the > default if that's what they'd like. Unfortunately, to do that > we need to start shipping an EXE launcher, probably with a > unique nam

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Liam Marsh added the comment: (uploaded file: dd.bmp) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Liam Marsh added the comment: """to do that we need to start shipping an EXE launcher, probably with a unique name (e.g. idle35-32.exe).""" nope, the windows packages already include an "idle.bat" launcher next to the "idle.py" and "idle.pyw" files. However, this launcher is (strangely enough)

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Steve Dower added the comment: It's possible, though personally I wouldn't like it (but I don't use IDLE, so I guess that makes the difference). I'd prefer to be able to list them all under the Open With menu, since that also allows users to easily make any of them the default if that's what t

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Terry J. Reedy added the comment: Liam, your question was answered in the technical sense in my two previous messages. However, being able to type 'python -m idlelib' instead of 'python -m idlelib.idle' is a separate issue from 'Edit with Idle' on the right context menu. Steve, is it possibl

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Liam Marsh added the comment: in fact, the idlelib.__main__ file exists in the 3.4 version... the question is: is it possible to make it exist on older versions? -- ___ Python tracker __

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Terry J. Reedy added the comment: Thanks for the link to where the doc *was* updated for 2.7. Currently, -m idlelib.idle works, so copying idle.py to __main__.py should make -m idlelib work. I will try this later, and see if the exact contents of idle.py are needed. Having '-m idlelib' work

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Ned Deily added the comment: Sorry, my apologies: I was testing incorrectly. Applying 556b9bafdee8 from Python 3 is not sufficient; there are still some other path import issues with extensions and icon files. But it shouldn't be hard to track those down and fix them, assuming supporting '-m

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Ned Deily added the comment: Perhaps I misunderstand what you meant but "python -m module_name" is a documented Python 2 feature: https://docs.python.org/2/using/cmdline.html#cmdoption-m I think the failure to initialize when using -m idlelib after copying over __main__.py from Python 3 is ca

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Terry J. Reedy added the comment: At one time, there would not have been any point. https://docs.python.org/3/library/__main__.html#module-__main__ contains this sentence "For a package, the same effect can be achieved by including a __main__.py module, the contents of which will be executed

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Zachary Ware added the comment: Terry J. Reedy added the comment: > Sorry. That has to be "py -3 ... " unless you have configured 'py' to run 3.x, or "py -m idlelib.idle ..." for 2.7. > Any reason not to add idlelib.__main__ to 2.7? It works the same in either version, as far as I can tell. --

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Terry J. Reedy added the comment: Sorry. That has to be "py -3 ... " unless you have configured 'py' to run 3.x, or "py -m idlelib.idle ..." for 2.7. -- ___ Python tracker ___

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Liam Marsh added the comment: the "py -m idlelib -e " command failed! (issue 23610 created) otherwise, yes, different versions of the "edit with idle" command sounds better. -- ___ Python tracker

[issue23546] Windows, 'Edit withIDLE', and multplie installed versions

Changes by Terry J. Reedy : -- title: Windows, IDLE and py.exe -> Windows, 'Edit withIDLE', and multplie installed versions ___ Python tracker ___ __