You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(8) |
Dec
(51) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(105) |
Feb
(93) |
Mar
(194) |
Apr
(145) |
May
(100) |
Jun
(111) |
Jul
(117) |
Aug
(126) |
Sep
(233) |
Oct
(138) |
Nov
(164) |
Dec
(109) |
2002 |
Jan
(216) |
Feb
(175) |
Mar
(216) |
Apr
(194) |
May
(157) |
Jun
(140) |
Jul
(158) |
Aug
(73) |
Sep
(105) |
Oct
(164) |
Nov
(104) |
Dec
(95) |
2003 |
Jan
(72) |
Feb
(69) |
Mar
(81) |
Apr
(151) |
May
(101) |
Jun
(139) |
Jul
(99) |
Aug
(118) |
Sep
(115) |
Oct
(151) |
Nov
(161) |
Dec
(102) |
2004 |
Jan
(120) |
Feb
(175) |
Mar
(106) |
Apr
(111) |
May
(54) |
Jun
(78) |
Jul
(76) |
Aug
(105) |
Sep
(94) |
Oct
(143) |
Nov
(75) |
Dec
(85) |
2005 |
Jan
(99) |
Feb
(77) |
Mar
(164) |
Apr
(97) |
May
(79) |
Jun
(57) |
Jul
(65) |
Aug
(102) |
Sep
(95) |
Oct
(129) |
Nov
(123) |
Dec
(52) |
2006 |
Jan
(48) |
Feb
(99) |
Mar
(90) |
Apr
(51) |
May
(81) |
Jun
(136) |
Jul
(56) |
Aug
(109) |
Sep
(50) |
Oct
(44) |
Nov
(74) |
Dec
(75) |
2007 |
Jan
(92) |
Feb
(137) |
Mar
(93) |
Apr
(79) |
May
(52) |
Jun
(74) |
Jul
(143) |
Aug
(175) |
Sep
(154) |
Oct
(137) |
Nov
(88) |
Dec
(90) |
2008 |
Jan
(58) |
Feb
(113) |
Mar
(167) |
Apr
(88) |
May
(105) |
Jun
(37) |
Jul
(87) |
Aug
(72) |
Sep
(56) |
Oct
(41) |
Nov
(102) |
Dec
(70) |
2009 |
Jan
(115) |
Feb
(113) |
Mar
(126) |
Apr
(58) |
May
(125) |
Jun
(45) |
Jul
(90) |
Aug
(125) |
Sep
(84) |
Oct
(61) |
Nov
(111) |
Dec
(61) |
2010 |
Jan
(85) |
Feb
(86) |
Mar
(130) |
Apr
(58) |
May
(57) |
Jun
(32) |
Jul
(25) |
Aug
(50) |
Sep
(41) |
Oct
(65) |
Nov
(63) |
Dec
(24) |
2011 |
Jan
(43) |
Feb
(31) |
Mar
(28) |
Apr
(68) |
May
(53) |
Jun
(42) |
Jul
(58) |
Aug
(26) |
Sep
(51) |
Oct
(76) |
Nov
(60) |
Dec
(9) |
2012 |
Jan
(16) |
Feb
(32) |
Mar
(32) |
Apr
(39) |
May
(16) |
Jun
(19) |
Jul
(3) |
Aug
(11) |
Sep
(35) |
Oct
(47) |
Nov
(28) |
Dec
(18) |
2013 |
Jan
(18) |
Feb
(36) |
Mar
(10) |
Apr
(7) |
May
(7) |
Jun
(27) |
Jul
(17) |
Aug
(35) |
Sep
(19) |
Oct
(31) |
Nov
(8) |
Dec
(22) |
2014 |
Jan
(5) |
Feb
(11) |
Mar
(18) |
Apr
(23) |
May
(26) |
Jun
(14) |
Jul
(18) |
Aug
(26) |
Sep
(20) |
Oct
(48) |
Nov
(13) |
Dec
(9) |
2015 |
Jan
(9) |
Feb
(15) |
Mar
(25) |
Apr
(10) |
May
(26) |
Jun
(6) |
Jul
(13) |
Aug
(5) |
Sep
(14) |
Oct
(36) |
Nov
(24) |
Dec
(18) |
2016 |
Jan
(24) |
Feb
(11) |
Mar
(1) |
Apr
(6) |
May
(7) |
Jun
(3) |
Jul
(9) |
Aug
(15) |
Sep
(22) |
Oct
(5) |
Nov
(5) |
Dec
(2) |
2017 |
Jan
(20) |
Feb
(4) |
Mar
(4) |
Apr
(1) |
May
(5) |
Jun
(7) |
Jul
(14) |
Aug
(9) |
Sep
(18) |
Oct
(2) |
Nov
(3) |
Dec
(3) |
2018 |
Jan
(7) |
Feb
(6) |
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(18) |
Sep
(8) |
Oct
(9) |
Nov
(4) |
Dec
(6) |
2019 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(4) |
May
(6) |
Jun
(8) |
Jul
(11) |
Aug
(10) |
Sep
(6) |
Oct
|
Nov
(1) |
Dec
|
2020 |
Jan
(8) |
Feb
(3) |
Mar
(1) |
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
(5) |
Nov
(2) |
Dec
(1) |
2021 |
Jan
|
Feb
|
Mar
(5) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(5) |
Jul
(15) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
(5) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jeff A. <ja...@fa...> - 2020-01-12 13:15:54
|
On 06/01/2020 15:49, Jeff Mitchell wrote: > I have found jython for 2.x to be exceedingly stable (thanks! > wonderful piece of work over the years!) .. though you need to halfway > recent for ssl/encryption changes and stability fixes. I'm glad you've found it so. Although familiar mostly with its flaws, now and then I stand far enough back to recognise how remarkable an achievement it is, and that I have the privilege of contributing to. > Hijacking the thread though .. any news on jython3, or is there just > nto enough volunteer manpower? Every few months I google up and only > find a repo from 2017, and various threads or questions but no > answers. (And I wish I had time to jump in and help, same as everyone..) > --> but is jython3 essentially dead for now? I don't think so. The main problem with that repo is that 2.7 moved on a lot since the fork, and since basic things like str changed from 2 to 3, there are technical problems merging. We also say amongst ourselves "we'll do that differently in 3" and it is difficult to see how you could, starting from there. 3 looks like a great opportunity for change, but the more one takes on, the longer it will be. Fortunately I have some time, but it has to be divided with 2.7. Jeff Allen > > On Mon, Jan 6, 2020 at 9:57 AM Stephen Gutz <sg...@hu... > <mailto:sg...@hu...>> wrote: > > Hi, > > I was wondering if there's a timeline for a non-beta release of > Jython. I'm happy to try out the version marked as beta, but I'd > prefer to wait if a non-beta release is imminent. > > For context, I'm currently working on upgrading my company's stack > to Java 11 which I believe requires upgrading Jython as well > (mainly because of the ASM version, I think). > > Thanks, > Steve > _______________________________________________ > Jython-users mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-users > > > > -- > > Jeff Mitchell > > Sr Application Architect > > Zayo | Our Fiber Fuels Global Innovation > > 1821 30th Street | Unit A | Boulder, CO 80301 > > Desk: 999.999.9999 | Cell: 999.999.9999 > > jef...@za... <mailto:jef...@za...> > > Purpose <http://zayo.is/signature-purpose>|Network Map > <http://zayo.is/signature-network>|LinkedIn > <http://zayo.is/signature-linkedin>| Twitter > <http://zayo.is/signature-twitter> > > > This communication is the property of Zayo and may contain > confidential or privileged information. If you have received this > communication in error, please promptly notify the sender by reply > e-mail and destroy all copies of the communication and any attachments. > |
From: Jeff A. <ja...@fa...> - 2020-01-12 12:16:36
|
On 06/01/2020 14:40, Stephen Gutz wrote: > Hi, > > I was wondering if there's a timeline for a non-beta release of > Jython. I'm happy to try out the version marked as beta, but I'd > prefer to wait if a non-beta release is imminent. I find putting dates to things has not been reliable but I'm happy to say what lies between us and a 2.7.2 full release. Issue https://bugs.jython.org/issue2834 looks like a blocker, not straightforward, and the fix sufficiently intrusive that we should not go straight to a release. So I expect the next thing to be a 2.7.2b3. Six other issues are also ear-marked 2.7.2: three look easy, two are probably not blockers, one may be. Jeff Allen |
From: Fabio Z. <fa...@gm...> - 2020-01-10 17:44:04
|
PyDev 7.5.0 Release Highlights - Fixed support for Python 3.8 (which wasn't properly added to 7.4.0). - Improved Cython support: - Cython itself is used to generate the AST for Cython files. - Cython needs to be available in the default interpreter. - Cython does not currently support generating the AST for files with errors, so, syntax errors must be fixed for the code-completion to work properly. - Debugger improvements (updated to pydevd 1.9.0). - Improved stepping into coroutines - Attach to process no longer needs to match the bitness of the target program with the interpreter. - File with a relative path is searched in sys.path folders (i.e.: so, cython builds can find the source). About PyDev PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and IronPython development, now also available for Python on Visual Studio Code. It comes with goodies such as code completion, syntax highlighting, syntax analysis, code analysis, refactor, debug, interactive console, etc. It is also available as a standalone through LiClipse with goodies such as multiple cursors, theming and support for many other languages, such as Django Templates, Jinja2, Html, JavaScript, etc. Links: PyDev: http://pydev.org PyDev Blog: http://pydev.blogspot.com PyDev on VSCode: http://pydev.org/vscode LiClipse: http://www.liclipse.com PyVmMonitor - Python Profiler: http://www.pyvmmonitor.com/ Cheers, Fabio Zadrozny |
From: Jeff M. <jef...@za...> - 2020-01-06 16:04:17
|
I have found jython for 2.x to be exceedingly stable (thanks! wonderful piece of work over the years!) .. though you need to halfway recent for ssl/encryption changes and stability fixes. Hijacking the thread though .. any news on jython3, or is there just nto enough volunteer manpower? Every few months I google up and only find a repo from 2017, and various threads or questions but no answers. (And I wish I had time to jump in and help, same as everyone..) --> but is jython3 essentially dead for now? On Mon, Jan 6, 2020 at 9:57 AM Stephen Gutz <sg...@hu...> wrote: > Hi, > > I was wondering if there's a timeline for a non-beta release of Jython. > I'm happy to try out the version marked as beta, but I'd prefer to wait if > a non-beta release is imminent. > > For context, I'm currently working on upgrading my company's stack to Java > 11 which I believe requires upgrading Jython as well (mainly because of the > ASM version, I think). > > Thanks, > Steve > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > -- Jeff Mitchell Sr Application Architect Zayo | Our Fiber Fuels Global Innovation 1821 30th Street | Unit A | Boulder, CO 80301 Desk: 999.999.9999 | Cell: 999.999.9999 jef...@za... Purpose <http://zayo.is/signature-purpose> | Network Map <http://zayo.is/signature-network> | LinkedIn <http://zayo.is/signature-linkedin> | Twitter <http://zayo.is/signature-twitter> This communication is the property of Zayo and may contain confidential or privileged information. If you have received this communication in error, please promptly notify the sender by reply e-mail and destroy all copies of the communication and any attachments. He who dies with the best barbecue sauce, wins. |
From: Stephen G. <sg...@hu...> - 2020-01-06 14:56:44
|
Hi, I was wondering if there's a timeline for a non-beta release of Jython. I'm happy to try out the version marked as beta, but I'd prefer to wait if a non-beta release is imminent. For context, I'm currently working on upgrading my company's stack to Java 11 which I believe requires upgrading Jython as well (mainly because of the ASM version, I think). Thanks, Steve |
From: <fwi...@gm...> - 2019-11-04 01:27:05
|
On behalf of the Jython development team, I'm pleased to announce that Jython 2.7.2b2 is released. Thanks to the many contributors to Jython. Details are here: https://fwierzbicki.blogspot.com/2019/11/jython-272b2-released.html -Frank |
From: Svata D. <ga...@vo...> - 2019-09-15 19:09:56
|
Hi, A project I am using utilizes Jython for scripting; invokes Jython using JSR 223 Stripting API: ScriptEngine engine = ... ; // obtain ScriptingEngine instance try (FileReader fr = new FileReader(file)) { return engine.eval(fr, context); } The file can script UI, so localized Strings (literals) may appear in the script file. Unless the entire application's default encoding *happens* to be correct (so that FileReader uses the correct one) + *all* the scripts use the encoding, the script text is naturally misread and national characters are garbled. When executing the file through PythonInterpreter.execfile(), one can declare encoding in the file explicitly: # coding=iso-8859-2 but that's not an option with ScriptEngine - the following error is thrown: javax.script.ScriptException: org.python.antlr.ParseException: org.python.antlr.ParseException: encoding declaration in Unicode string I sort of understand that, since the passed Reader should have already decoded the representation. Sadly if I have scripts that can be invoked (also) by other scripts, those scripts HAVE to contain #coding directive for execfile() call in Python script. Given the exception above, they cannot be invoked directly from Java using JSR223 APIs. How to solve that situation ? I can naturally provide a clever Reader that reads top of the file according to PEP-263 and then passes a Reader that decodes the source correctly. But that would have to be replicated in other apps using JSR-223 API _and_ entangles the project with Python-specific processing, which does not seem "right". Is there a more appropriate solution for this issue ? Thanks for the help, -Svata |
From: Jeff M. <jef...@za...> - 2019-09-13 20:31:47
|
Its hard (in an OS independant fashion) to know if a file is _open_, but its a little easier to tell if it is _locked_, which is the same for you likely. (If a job opens a file without locking it, then you couldn't easily detect it.) Without creating your own file locking scheme, or looking into the OS specific flock functions, you could just take a look at.. https://pypi.org/project/filelock/2.0.13/ On Fri, Sep 13, 2019 at 4:26 PM Pete via Jython-users < jyt...@li...> wrote: > I need to append and then close a file. > > I am trying to avoid file write contention issues. > > How can I determine if the file if not closed before opening it for append? > > > Thank you, > > PR > > > > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > |
From: Pete <pr...@ya...> - 2019-09-13 20:26:34
|
I need to append and then close a file. I am trying to avoid file write contention issues. How can I determine if the file if not closed before opening it for append? Thank you, PR |
From: Pekka K. <pe...@ik...> - 2019-09-02 22:01:14
|
Jim Baker wrote:: > > +100 > > I like this well-considered compromise. Source compatibility with Java 7 ensures it is possible for a self service model if there are users who actually need Java 7. Meanwhile we are able to ensure all of our dependencies are supported, which is key for any release. +1 > This approach also gives an immediate path forward to being on Java 11, the only current LTS option, for a Jython 2.7.3, as well as setting up for Jython 3.x development. Has there been discussion lately about Jython 2.7.3 vs Jython 3? I'd personally like to see all efforts concentrated on Jython 3 once Jython 2.7.2 is out. Python 2 EOL being very near, more and more projects are dropping Python 2 support and at the same time they drop Jython support as well. For us Jython support is the primary reason to support Python 2 still after the EOL, but I cannot see us doing it past 2020 anymore. Cheers, .peke -- Agile Tester/Developer/Consultant :: http://eliga.fi Lead Developer of Robot Framework :: http://robotframework.org |
From: Jim B. <jim...@py...> - 2019-09-01 14:29:29
|
+100 I like this well-considered compromise. Source compatibility with Java 7 ensures it is possible for a self service model if there are users who actually need Java 7. Meanwhile we are able to ensure all of our dependencies are supported, which is key for any release. This approach also gives an immediate path forward to being on Java 11, the only current LTS option, for a Jython 2.7.3, as well as setting up for Jython 3.x development. - Jim On Sun, Sep 1, 2019 at 4:11 AM Jeff Allen <ja...@fa...> wrote: > It is a fact that we remain source-compatible with Java 7. We test on 7, > 8 and 11 in the CI. > > Java 7 is past EOL, and no-one should really be using it in production, > but a few may still be running Jython on it. (No-one has said they are, > so it's at best a reasonable conjecture.) I have observed test failures > with SSL on Java 7, that disappear on Java 8, since upgrading the BC > jars to satisfy security concerns. > > I propose we compile releases up to 2.7.2 final with Java 8, and for the > Java 8 target. (It really doesn't seem right to compile it with an > unsupported Java 7.) This means the Jython that users download will > require a minimum of Java 8 to run. We support up to Java 11, with > reasonable confidence beyond that. > > But we remain source-compatible with Java 7 up to 2.7.2 final. Then, if > a user really needs a version that runs on Java 7, we can show them how > to build one. I believe it is a matter of defining properties in or > around the Ant build, down-grading the BC JARs if need be, and making a > snapshot installer. It will be an "unofficial" build that we do not > undertake to support, and comes with a number of (additional) known > defects. > > Good compromise? > > Jeff > > Jeff Allen > > On 26/07/2019 21:54, Jeff Allen wrote: > > When the project set out to create Jython 2.7.2, it was reasonable > > still to support Java 7. Now we find ourselves on the verge of a 2.7.2 > > beta release, Java 8 seems the logical minimum. We currently build and > > test on Java 7 but some things would resolve themselves if we could > > move on. We intend to support "before and after Jigsaw" JVMs (say 8 > > and 11). > > > > Straw poll: does anyone amongst our users have a good reason why > > Jython 2.7.2 should run on Java 7? > > > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jeff A. <ja...@fa...> - 2019-09-01 10:11:48
|
It is a fact that we remain source-compatible with Java 7. We test on 7, 8 and 11 in the CI. Java 7 is past EOL, and no-one should really be using it in production, but a few may still be running Jython on it. (No-one has said they are, so it's at best a reasonable conjecture.) I have observed test failures with SSL on Java 7, that disappear on Java 8, since upgrading the BC jars to satisfy security concerns. I propose we compile releases up to 2.7.2 final with Java 8, and for the Java 8 target. (It really doesn't seem right to compile it with an unsupported Java 7.) This means the Jython that users download will require a minimum of Java 8 to run. We support up to Java 11, with reasonable confidence beyond that. But we remain source-compatible with Java 7 up to 2.7.2 final. Then, if a user really needs a version that runs on Java 7, we can show them how to build one. I believe it is a matter of defining properties in or around the Ant build, down-grading the BC JARs if need be, and making a snapshot installer. It will be an "unofficial" build that we do not undertake to support, and comes with a number of (additional) known defects. Good compromise? Jeff Jeff Allen On 26/07/2019 21:54, Jeff Allen wrote: > When the project set out to create Jython 2.7.2, it was reasonable > still to support Java 7. Now we find ourselves on the verge of a 2.7.2 > beta release, Java 8 seems the logical minimum. We currently build and > test on Java 7 but some things would resolve themselves if we could > move on. We intend to support "before and after Jigsaw" JVMs (say 8 > and 11). > > Straw poll: does anyone amongst our users have a good reason why > Jython 2.7.2 should run on Java 7? > |
From: Stefan R. <ste...@gm...> - 2019-08-30 16:49:14
|
Even if you were able to dex Jython.jar, Jython would still generate Java bytecode at runtime. AFAIK there is no way to dex this at runtime on Android. Even if it was possible or if Jython could generate dexed bytecode directly, AFAIK Android prohibits apps to load such new code at runtime. I used to think that it should be possible at least to create all bytecode required for a certain Python porgram or library ahead of time and dex it, but was told that Jython in its current form inherently needs to generate, load and run bytecode at runtime. I.e. some bits for gluing code cannot be created ahead of time. Best feasible workaround would be to use CPython bytecode on Android. Jython can actually read and interpret CPython bytecode (.pyc files). However, it cannot create it: That part was never ported from CPython and it is significant work (about 10k lines of C-code need to be ported to Java for this). We used to have this particular task open as a GSoC project proposal: https://github.com/jythontools/gsoc2015#python-bytecode-compiler However, nobody ever applied for this project. -Stefan Am Fr., 30. Aug. 2019 um 16:06 Uhr schrieb Jeff Mitchell < jef...@za...>: > This begs the question.. if you know the command line, do it yourself? > Also, jython 2.5 is pretty old; why not 2.7.x? > > (I don't know what dex is, haven't done Android dev) > > On Thu, Aug 29, 2019 at 9:49 PM HemanthJabalpuri < > hem...@gm...> wrote: > >> Can someone please dex the jython-standalone-2.5.3.jar using dx tool.from >> android sdk. >> dx --dex --min-sdk-version=1 --output="jython-standalone-2.5.3-dexed.jar" >> jython-standalone-2.5.3.jar >> >> Thanks >> _______________________________________________ >> Jython-users mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-users >> > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > |
From: Jeff M. <jef...@za...> - 2019-08-30 14:06:04
|
This begs the question.. if you know the command line, do it yourself? Also, jython 2.5 is pretty old; why not 2.7.x? (I don't know what dex is, haven't done Android dev) On Thu, Aug 29, 2019 at 9:49 PM HemanthJabalpuri <hem...@gm...> wrote: > Can someone please dex the jython-standalone-2.5.3.jar using dx tool.from > android sdk. > dx --dex --min-sdk-version=1 --output="jython-standalone-2.5.3-dexed.jar" > jython-standalone-2.5.3.jar > > Thanks > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > |
From: HemanthJabalpuri <hem...@gm...> - 2019-08-30 01:49:11
|
Can someone please dex the jython-standalone-2.5.3.jar using dx tool.from android sdk. dx --dex --min-sdk-version=1 --output="jython-standalone-2.5.3-dexed.jar" jython-standalone-2.5.3.jar Thanks |
From: Houtman, R. <Rol...@nl...> - 2019-08-20 11:40:36
|
Straw poll answer: No Java 7 required from my side. However support for Java 11+ is demanded from our clients in near future. -----Original Message----- From: Jeff Allen <ja...@fa...> Sent: Friday, July 26, 2019 10:55 PM To: jyt...@li... Cc: Jython Developers <jyt...@li...> Subject: [Jython-users] Java 7 or 8? When the project set out to create Jython 2.7.2, it was reasonable still to support Java 7. Now we find ourselves on the verge of a 2.7.2 beta release, Java 8 seems the logical minimum. We currently build and test on Java 7 but some things would resolve themselves if we could move on. We intend to support "before and after Jigsaw" JVMs (say 8 and 11). Straw poll: does anyone amongst our users have a good reason why Jython 2.7.2 should run on Java 7? -- Jeff Allen _______________________________________________ Jython-users mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-users |
From: Jeff A. <ja...@fa...> - 2019-08-13 19:21:56
|
It can't find the class, so it is probably not a problem with UTF-8. I don't understand why JNI is mentioned, but the inner exception suggests the jython JAR is not on the class path, either at compile time or run-time. Jeff Allen On 13/08/2019 12:34, Евгений Король wrote: > Hello. I try to use Russian in Jython under Java. I found example like this: > PythonInterpreter interpreter = new PythonInterpreter() { > { > cflags = new CompilerFlags(CompilerFlags.PyCF_SOURCE_IS_UTF8); > } > }; > > And when i use it in Java it works and Jython is output in Unicode. > But when i compile it with Java Compiler API i have this error: > Error: A JNI error has occurred, please check your installation and try again > Exception in thread "main" java.lang.NoClassDefFoundError: > org/python/util/PythonInterpreter > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Unknown Source) > at java.lang.Class.privateGetMethodRecursive(Unknown Source) > at java.lang.Class.getMethod0(Unknown Source) > at java.lang.Class.getMethod(Unknown Source) > at sun.launcher.LauncherHelper.validateMainClass(Unknown Source) > at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source) > Caused by: java.lang.ClassNotFoundException: org.python.util.PythonInterpreter > at java.net.URLClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > ... 7 more > > What i can do? > > > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > |
From: Евгений К. <ff...@gm...> - 2019-08-13 11:34:53
|
Hello. I try to use Russian in Jython under Java. I found example like this: PythonInterpreter interpreter = new PythonInterpreter() { { cflags = new CompilerFlags(CompilerFlags.PyCF_SOURCE_IS_UTF8); } }; And when i use it in Java it works and Jython is output in Unicode. But when i compile it with Java Compiler API i have this error: Error: A JNI error has occurred, please check your installation and try again Exception in thread "main" java.lang.NoClassDefFoundError: org/python/util/PythonInterpreter at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.lang.Class.privateGetMethodRecursive(Unknown Source) at java.lang.Class.getMethod0(Unknown Source) at java.lang.Class.getMethod(Unknown Source) at sun.launcher.LauncherHelper.validateMainClass(Unknown Source) at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source) Caused by: java.lang.ClassNotFoundException: org.python.util.PythonInterpreter at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 7 more What i can do? |
From: Евгений К. <ff...@gm...> - 2019-08-13 11:32:29
|
Hello. I try to use Russian in Jython under Java. I found example like this: |
From: Jeff A. <ja...@fa...> - 2019-08-10 06:49:06
|
On 27/07/2019 17:32, James Klo via Jython-users wrote: > [snipped lots of other good points] > > Jeff mentions: >> >> We currently build and test >> on Java 7 but some things would resolve themselves if we >> could move on. >> > > Could there be some elaboration here? What issues on the 2.7.2 > milestone would be solved by moving to J8? Pluses and minuses here > would be helpful. I was thinking of: * https://bugs.jython.org/issue2770 (SSL test failures) * I wrote a substitute base64 decoder in https://bugs.jython.org/issue2663 (which was fun, but it could be removed at Java 8). * The odd place where a lambda would save nugatory work (logging). Only the first is an actual problem for users (who have to downgrade their JAR to match their insecure JVM). There may be other bugs we didn't consider blockers that are also 7-isms. Jeff Jeff Allen |
From: Adam B. <ada...@gm...> - 2019-08-09 20:13:12
|
Hi there The quick answer is it’s mostly driven by the value of Charset.defaultCharset(). This can be set by Java runtime property -Dfile.encoding at startup. Note that the console you are using has to actually support it. Away from a computer right now, so excuse the lack of a proper code snippet. Cheers Adam > 在 2019年8月9日,上午11:03,Евгений Король <ff...@gm...> 写道: > > Hello. How to set encoding in Jython when using it on Java like > PythonInterpreter? > When i print russians words its write only ???? > > > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users |
From: Евгений К. <ff...@gm...> - 2019-08-09 10:03:19
|
Hello. How to set encoding in Jython when using it on Java like PythonInterpreter? When i print russians words its write only ???? |
From: Hasan D. <has...@gm...> - 2019-07-27 19:57:05
|
Santhosh, On Sat, 27 Jul 2019 at 12:36, Santhosh Kumar J <san...@ou...> wrote: > Is there any solution to the problem i'm facing? > You can embed the .py in your jar file and load it like this: public static void exec() { PythonInterpreter interp = new PythonInterpreter(); StringWriter outputFromJython = new StringWriter(); interp.setOut(outputFromJython); interp.execfile(inputStreamRepreesntingPyFile); // outputFromJython contains output of execing script } -- OpenPGP: https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1 If you wish to request my time, please do so using *bit.ly/hd1AppointmentRequest <http://bit.ly/hd1AppointmentRequest>*. Si vous voudrais faire connnaisance, allez a *bit.ly/hd1AppointmentRequest <http://bit.ly/hd1AppointmentRequest>*. <https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1>Sent from my mobile device Envoye de mon portable |
From: Santhosh K. J <san...@ou...> - 2019-07-27 19:36:50
|
Thanks for your response. Is there any new/updated documentation for the same? And also, is there any solution to the problem i'm facing.? Thanks, Santhosh On 28-Jul-2019, at 12:36 AM, Hasan Diwan <has...@gm...<mailto:has...@gm...>> wrote: Santhosh, On Sat, 27 Jul 2019 at 12:01, Santhosh Kumar J <san...@ou...<mailto:san...@ou...>> wrote: I'm using jython 2.7.0 The wiki page you linked to has not been updated in a decade(https://wiki.python.org/jython/JythonFaq/DistributingJythonScripts -- "last updated" line). I would posit that things have changed in the past decade. -- H -- OpenPGP: https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1 If you wish to request my time, please do so using bit.ly/hd1AppointmentRequest<http://bit.ly/hd1AppointmentRequest>. Si vous voudrais faire connnaisance, allez a bit.ly/hd1AppointmentRequest<http://bit.ly/hd1AppointmentRequest>. <https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1>Sent from my mobile device Envoye de mon portable _______________________________________________ Jython-users mailing list Jyt...@li...<mailto:Jyt...@li...> https://lists.sourceforge.net/lists/listinfo/jython-users |
From: Hasan D. <has...@gm...> - 2019-07-27 19:06:21
|
Santhosh, On Sat, 27 Jul 2019 at 12:01, Santhosh Kumar J <san...@ou...> wrote: > I'm using jython 2.7.0 > The wiki page you linked to has not been updated in a decade( https://wiki.python.org/jython/JythonFaq/DistributingJythonScripts -- "last updated" line). I would posit that things have changed in the past decade. -- H -- OpenPGP: https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1 If you wish to request my time, please do so using *bit.ly/hd1AppointmentRequest <http://bit.ly/hd1AppointmentRequest>*. Si vous voudrais faire connnaisance, allez a *bit.ly/hd1AppointmentRequest <http://bit.ly/hd1AppointmentRequest>*. <https://sks-keyservers.net/pks/lookup?op=get&search=0xFEBAD7FFD041BBA1>Sent from my mobile device Envoye de mon portable |