Issue2206

classification
Title: Jython script file names and file type associations on Windows
Type: behaviour Severity: normal
Components: Core Versions:
Milestone:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: eaaltonen, zyasoft
Priority: Keywords:

Created on 2014-09-11.11:16:12 by eaaltonen, last changed 2014-09-16.23:01:38 by zyasoft.

Messages
msg8990 (view) Author: (eaaltonen) Date: 2014-09-11.11:26:05
The motivation for this ticket is to have jython scripts registered as executable targets (in Windows).

Windows apparently does not have an equivalent of shebang mechanism in Unix, which would allow specifying the interpreter as jython.

Possible way of solving the use case is renaming jython script as .jy files, which allows setting a file type association to jython.bat.

This however produces new conflict, because trying to import from a .jy script fails.

Earlier mailing list discussions:
http://sourceforge.net/p/jython/mailman/message/10227358/
http://sourceforge.net/p/jython/mailman/message/10226002/
http://sourceforge.net/p/jython/mailman/message/11764221/

Hoping for the following outcomes:
a) some other way of getting jython scripts associated with the jython.bat
b) approval for supporting import both from .py and .jy files.
c) Something else I didn't think of
msg9004 (view) Author: Jim Baker (zyasoft) Date: 2014-09-16.23:01:38
In general, this proposal is not a workable idea - so much Python code expects .py extensions for modules, including in the standard library.

As mentioned, it is possible to run a script in Jython using an arbitrary extension, so for scripts, if not modules, making this association on Windows is certainly feasible. I don't know if there's a reason for us to explicitly support however.
History
Date User Action Args
2014-09-16 23:01:38zyasoftsetstatus: open -> closed
resolution: wont fix
messages: + msg9004
nosy: + zyasoft
2014-09-11 11:26:08eaaltonensetmessages: + msg8990
2014-09-11 11:16:12eaaltonencreate