[issue23546] windows, IDLE and pep 397

2015-03-06 Thread Terry J. Reedy

Terry J. Reedy added the comment:

To be more exact, (I believe) 'Edit with Idle' runs the equivalent of ' 
-m idlelib -e ' where  is the current default python (ad  
is the file right-clicked on).  Idle just goes alone for the ride.  You are 
proposing more or less that  be replaced with 'py'.

The problems with this are that it is still opaque which version of python (and 
hence Idle) will be run, there is no way to select the version to be run, most 
people do not use #! on Windows, especially beginners, and some people want to 
be able to open, edit, and run a file on both 2.x and 3.x (currently most often 
2.7 and 3.4).

This same issue has come up on stackoverflow.  To me, a much better solution 
would be an explicit 'Open with Idle x.y' on the context menu for each version 
of Idle installed.  This would be explicit and allow version selection.  (I am 
obviously proposing that the 2.7 and 3.4 installers be tweaked also.)

--
nosy: +terry.reedy

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue23546] windows, IDLE and pep 397

2015-02-28 Thread SilentGhost

Changes by SilentGhost :


--
components: +Installation
versions:  -Python 2.7, Python 3.2, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue23546] windows, IDLE and pep 397

2015-02-28 Thread Liam Marsh

New submission from Liam Marsh:

hello,
pep 397 describes a "Python launcher for the Windows platform.
A Python launcher is a single executable which uses a number of 
heuristics to locate a Python executable and launch it with a
specified command line."

Problem: that affects only the "open" file action behavior, and not the "EDIT 
with idle" file action behavior, and then it is the last installed IDLE who 
wins.
the problem is not the IDLE changes themselves, but that one version's IDLE can 
only run the edited script in its version, and ignoring the shebang.

Could the windows installer install a third executable (for ex: pyi.exe)
which launch the correct IDLE according to the shebang line of the edited file?
Or maybe it should be done using "pyw.exe /edit "...

Than you for reading this and have a nice day/evening!

--
components: IDLE, Windows
messages: 236870
nosy: Liam.Marsh, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: windows, IDLE and pep 397
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com