From: Raphail <raf...@ho...> - 2019-05-20 14:09:05
|
I have several hundreds of python scripts that had been running with Jython 2.2.1 until now. This version consumes so much less space in storage memory than 2.7, and when I compared those 2, the first one also consumed less memory on my server startup (about 8MB less). All in all, I don't want to perform an update that no matter how I look at it, has no benefits for my application (e.g. my project already contains libraries such as mysql connector and such) and I'm forced to either continue with 2.2.1 and its unknown lifespan or probably give up Jython and rewrite all my scripts to Java. It would be really cool if there was a version that excluded all those external libraries and such, and was more friendly in terms of consuming storage space. -- Sent from: http://python.6.x6.nabble.com/jython-dev-f1778516.html |
From: Adam B. <ada...@gm...> - 2019-05-21 03:45:34
|
Hi Raphail The dev team are working on a gradle build, one of the outputs of which would be a slim jar as you describe. If you look on jython trunk, there is already an experimental build.gradle there. You may be able to use that to build an experimental jython-only jar. It's a complex part of the build, so if you know gradle well, I think patches are also welcome. Cheers Adam On Tue, 21 May 2019 at 00:09, Raphail <raf...@ho...> wrote: > I have several hundreds of python scripts that had been running with Jython > 2.2.1 until now. > This version consumes so much less space in storage memory than 2.7, and > when I compared those 2, the first one also consumed less memory on my > server startup (about 8MB less). All in all, I don't want to perform an > update that no matter how I look at it, has no benefits for my application > (e.g. my project already contains libraries such as mysql connector and > such) and I'm forced to either continue with 2.2.1 and its unknown lifespan > or probably give up Jython and rewrite all my scripts to Java. > > It would be really cool if there was a version that excluded all those > external libraries and such, and was more friendly in terms of consuming > storage space. > > > > -- > Sent from: http://python.6.x6.nabble.com/jython-dev-f1778516.html > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jeff A. <ja...@fa...> - 2019-05-21 07:23:40
|
Would the dependencies dragged into memory as Jython starts not amount to the same footprint? Maybe not if the problem is scanning all those JARs we have. WBNI Jython started quickly and used only the memory it needed. In my mind, that depends on rationalising and enriching our logging, a need I've felt in several pieces of work over the last year. I think we'd learn a lot. Jeff Jeff Allen On 21/05/2019 04:45, Adam Burke wrote: > Hi Raphail > > The dev team are working on a gradle build, one of the outputs of > which would be a slim jar as you describe. > > If you look on jython trunk, there is already an experimental > build.gradle there. You may be able to use that to build an > experimental jython-only jar. > > It's a complex part of the build, so if you know gradle well, I think > patches are also welcome. > > Cheers > Adam > > On Tue, 21 May 2019 at 00:09, Raphail <raf...@ho... > <mailto:raf...@ho...>> wrote: > > I have several hundreds of python scripts that had been running > with Jython > 2.2.1 until now. > This version consumes so much less space in storage memory than > 2.7, and > when I compared those 2, the first one also consumed less memory on my > server startup (about 8MB less). All in all, I don't want to > perform an > update that no matter how I look at it, has no benefits for my > application > (e.g. my project already contains libraries such as mysql > connector and > such) and I'm forced to either continue with 2.2.1 and its unknown > lifespan > or probably give up Jython and rewrite all my scripts to Java. > > It would be really cool if there was a version that excluded all those > external libraries and such, and was more friendly in terms of > consuming > storage space. > > > > -- > Sent from: http://python.6.x6.nabble.com/jython-dev-f1778516.html > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
From: Jeff A. <ja...@fa...> - 2019-09-08 20:39:40
|
I've noticed that the "project name" for the Gradle-built JAR cannot be "jython", because we already publish that (being the fat jar). I propose therefore to name it "jython-slim", in honour of this thread. It's experimental anyway: I don't have much confidence it is correctly built. I could really do with writing an application with it as a dependency. (Or others doing so during beta.) Jeff Allen On 21/05/2019 04:45, Adam Burke wrote: > Hi Raphail > > The dev team are working on a gradle build, one of the outputs of > which would be a slim jar as you describe. > > If you look on jython trunk, there is already an experimental > build.gradle there. You may be able to use that to build an > experimental jython-only jar. > > It's a complex part of the build, so if you know gradle well, I think > patches are also welcome. > > Cheers > Adam > > On Tue, 21 May 2019 at 00:09, Raphail <raf...@ho... > <mailto:raf...@ho...>> wrote: > > I have several hundreds of python scripts that had been running > with Jython > 2.2.1 until now. > This version consumes so much less space in storage memory than > 2.7, and > when I compared those 2, the first one also consumed less memory on my > server startup (about 8MB less). All in all, I don't want to > perform an > update that no matter how I look at it, has no benefits for my > application > (e.g. my project already contains libraries such as mysql > connector and > such) and I'm forced to either continue with 2.2.1 and its unknown > lifespan > or probably give up Jython and rewrite all my scripts to Java. > > It would be really cool if there was a version that excluded all those > external libraries and such, and was more friendly in terms of > consuming > storage space. > > > > -- > Sent from: http://python.6.x6.nabble.com/jython-dev-f1778516.html > > |
From: Eero A. <eer...@ik...> - 2019-09-09 08:03:24
|
There is a use case that is related to the JAR split of Jython: Using Jython to create a sandboxed scripting environment. That use case would call for some more fine grained splitting of the Jython implementation. Policy permissions are granted by either by code signature or location https://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.html For the sandboxed scripting use case one would probably want to have the Jython class loader in it's own JAR in order to restrict class loading in there only. I understand a lot of more work would still be involved in serving this use case, but you could split this as a reservation, if a new jar layout is being taken into use. Eero Aaltonen On Sun, Sep 8, 2019 at 11:40 PM Jeff Allen <ja...@fa...> wrote: > I've noticed that the "project name" for the Gradle-built JAR cannot be > "jython", because we already publish that (being the fat jar). I propose > therefore to name it "jython-slim", in honour of this thread. > > It's experimental anyway: I don't have much confidence it is correctly > built. I could really do with writing an application with it as a > dependency. (Or others doing so during beta.) > > Jeff Allen > > On 21/05/2019 04:45, Adam Burke wrote: > > Hi Raphail > > > > The dev team are working on a gradle build, one of the outputs of > > which would be a slim jar as you describe. > > > > If you look on jython trunk, there is already an experimental > > build.gradle there. You may be able to use that to build an > > experimental jython-only jar. > > > > It's a complex part of the build, so if you know gradle well, I think > > patches are also welcome. > > > > Cheers > > Adam > > > |