Re: LiJy-launch

Jim Baker <[email protected]>
Newsgroups gmane.comp.lang.jython.devel
Message-ID <CAOhO=aOmnzh-mZF5X1OUY9w0NFfjyO=Lo-FhANxYfCDhCcK6Wg@mail.gmail.com>
FWIW, as of RC3, bin/jython.py -> bin/jython on platforms that support
CPython 2.7. This can be readily relaxed and backported to CPython 2.5 or
possibly CPython 2.4.

My feeling is that we should package dependencies like this, with different
license restrictions, in PyPI, eg we should support

pip install lijy

and they have a new launcher installed. There is a similar procedure for
JRuby, https://rubygems.org/gems/jruby-launcher/versions/1.1.1-java; the
process of compiling and linking could support systems we don't have wheels
built for.

Probably we should save the old launcher somewhere, so recovery could be
done.

One problem is that Windows, unlike Unix-like systems, has no built-in
support for replacing a file that is in-use, other than using old utilities
like inuse.exe (https://support.microsoft.com/en-us/kb/927229)

- Jim

On Sat, May 9, 2015 at 7:19 AM, Stefan Richthofer <[email protected]>
wrote:

> Hi all,
>
> as kind of side-quest I have been working to write a JNI-based
> Jython-launcher
> with the mid-term goal to replace the current one that needs to bundle
> CPython.
> (I couldn't resist to make up some fancy development-name for the project.)
> It turned out to be much harder than I thought, but finally, here is kind
> of a
> prototype (for now linux only).
> I would appreciate some testing from the linux-users among you, before I
> start
> porting it to windows.
>
> Take a look at
> https://github.com/Stewori/LiJy-launch (I wanna see some stars!)
> Yes, the source code needs lots of clean-up; first do things right ;)
>
> I'd like to see this become the default-launcher in Jython 2.7.1, but
> unfortunately
> there might be license issues. It was infeasible to write this launcher
> without
> including source-code from Open JDK, which is released under GPLv2 with
> classpath exception. However this would not be infective for Jython as
> there is
> the classpath exception and Jython would not link to the launcher anyway
> (it's only
> the other way round).
> Only thing is that if Jython would distribute this launcher, it would have
> to
> clarify that the launcher is GPLv2 with classpath exception as opposed to
> the rest
> of Jython and include the according license text-file.
> I suppose this should be okay, what do you think?
>
> Regards
>
> Stefan
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Jython-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>



-- 
- Jim

jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com}
twitter.com/jimbaker
github.com/jimbaker
bitbucket.com/jimbaker

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.