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 <filepath>"...
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 <rep...@bugs.python.org>
<http://bugs.python.org/issue23546>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
