Message10657

OK, after a chat with Jim (@zyasoft, feel free to comment if i missed anythin) offline about this issue. Here's the somewhat new proposal:

As we do today we look for python.executable property. If that does not exist, instead of None, we will return sys.perfix + bin/jython(.exe) depending on the platform.

The jython file may not exist, but it gives users the ability to install/write a wrapper that would work, especially in cases where someone does want to spawn/fork from existing standalone jar. It should also work nicely with custom filesystems if proper wrappers are generated (will not implement as part of this issue).

And just to reiterate, it is still customizable via -Dpython.executable.

This diverges from Jython 2.7.0, but as i said before i could not actually find any use of it on the internet (does not mean it does not exist of course), but i think the benefit outweighs the risk (being closer to CPython implementation for one).