Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(38) |
Nov
(98) |
Dec
(58) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(114) |
Feb
(123) |
Mar
(96) |
Apr
(66) |
May
(84) |
Jun
(72) |
Jul
(128) |
Aug
(126) |
Sep
(82) |
Oct
(80) |
Nov
(148) |
Dec
(55) |
| 2002 |
Jan
(137) |
Feb
(85) |
Mar
(118) |
Apr
(67) |
May
(71) |
Jun
(28) |
Jul
(69) |
Aug
(48) |
Sep
(83) |
Oct
(79) |
Nov
(54) |
Dec
(32) |
| 2003 |
Jan
(44) |
Feb
(47) |
Mar
(59) |
Apr
(57) |
May
(43) |
Jun
(45) |
Jul
(44) |
Aug
(39) |
Sep
(27) |
Oct
(62) |
Nov
(17) |
Dec
(23) |
| 2004 |
Jan
(41) |
Feb
(51) |
Mar
(38) |
Apr
(30) |
May
(25) |
Jun
(12) |
Jul
(11) |
Aug
(27) |
Sep
(16) |
Oct
(56) |
Nov
(23) |
Dec
(29) |
| 2005 |
Jan
(75) |
Feb
(82) |
Mar
(50) |
Apr
(77) |
May
(19) |
Jun
(104) |
Jul
(47) |
Aug
(42) |
Sep
(28) |
Oct
(143) |
Nov
(62) |
Dec
(13) |
| 2006 |
Jan
(20) |
Feb
(10) |
Mar
(59) |
Apr
(45) |
May
(25) |
Jun
(129) |
Jul
(162) |
Aug
(91) |
Sep
(15) |
Oct
(39) |
Nov
(186) |
Dec
(191) |
| 2007 |
Jan
(134) |
Feb
(140) |
Mar
(106) |
Apr
(77) |
May
(92) |
Jun
(63) |
Jul
(233) |
Aug
(102) |
Sep
(119) |
Oct
(63) |
Nov
(68) |
Dec
(32) |
| 2008 |
Jan
(69) |
Feb
(91) |
Mar
(129) |
Apr
(44) |
May
(18) |
Jun
(53) |
Jul
(50) |
Aug
(25) |
Sep
(11) |
Oct
(28) |
Nov
(67) |
Dec
(36) |
| 2009 |
Jan
(20) |
Feb
(24) |
Mar
(66) |
Apr
(53) |
May
(48) |
Jun
(48) |
Jul
(59) |
Aug
(82) |
Sep
(49) |
Oct
(30) |
Nov
(16) |
Dec
(16) |
| 2010 |
Jan
(52) |
Feb
(25) |
Mar
(36) |
Apr
(34) |
May
(14) |
Jun
(15) |
Jul
(14) |
Aug
(16) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(22) |
Mar
(45) |
Apr
(9) |
May
(8) |
Jun
(13) |
Jul
(12) |
Aug
(4) |
Sep
(6) |
Oct
(10) |
Nov
(21) |
Dec
(5) |
| 2012 |
Jan
(6) |
Feb
(9) |
Mar
(25) |
Apr
(6) |
May
(4) |
Jun
(23) |
Jul
(6) |
Aug
(18) |
Sep
(21) |
Oct
(34) |
Nov
(19) |
Dec
(25) |
| 2013 |
Jan
(8) |
Feb
(34) |
Mar
(35) |
Apr
(4) |
May
(11) |
Jun
(4) |
Jul
(7) |
Aug
(5) |
Sep
(20) |
Oct
(12) |
Nov
(11) |
Dec
(7) |
| 2014 |
Jan
(10) |
Feb
(18) |
Mar
(50) |
Apr
(26) |
May
(53) |
Jun
(21) |
Jul
(12) |
Aug
(39) |
Sep
(43) |
Oct
(26) |
Nov
(8) |
Dec
(6) |
| 2015 |
Jan
(18) |
Feb
(32) |
Mar
(31) |
Apr
(42) |
May
(38) |
Jun
(13) |
Jul
(6) |
Aug
(11) |
Sep
(29) |
Oct
(25) |
Nov
(10) |
Dec
(11) |
| 2016 |
Jan
(24) |
Feb
(12) |
Mar
(13) |
Apr
(15) |
May
(22) |
Jun
(8) |
Jul
(12) |
Aug
(25) |
Sep
(8) |
Oct
(6) |
Nov
(13) |
Dec
(7) |
| 2017 |
Jan
(6) |
Feb
(29) |
Mar
(32) |
Apr
(8) |
May
(82) |
Jun
(42) |
Jul
(20) |
Aug
(17) |
Sep
(27) |
Oct
(14) |
Nov
(22) |
Dec
(6) |
| 2018 |
Jan
(12) |
Feb
(9) |
Mar
(22) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jeff Allen <ja.py@fa...> - 2018-04-20 07:21:09
|
My solution is to use the IDE as a debugger but not let it compile the code for me. Can't say how to do that in IntelliJ. I use Eclipse and that builds with ant (if configured carefully), but I don't get reliable results that way. By default it will compile incrementally (and continuously), which I suppress. The IDE builds with a different compiler from the system one, which has produced weird results in the past. At the moment I'm compiling with 7 and running with 9 so I'd really rather the IDE stay out of it. Because it is constantly checking the code, the IDE lists hundreds of undefined symbols on a new copy of the code base until I re-discover which JAR files to add to the build path from the extlibs folder. I could give my current list here but the process is easily driven by looking for failing import statements and doing an Internet search for the package if I can't guess. More undefined symbols turn up when I debug because I step into jars that need jars that need jars ... The part it seems impossible to get entirely right is the use of the "exposed" files. Either the IDE can't find some symbols (just a few), or it can't find the associated source: I can choose which by re-ordering the path. When I debug, I use remote debugging. I start Jython at a shell prompt and connect the IDE to it. I have a launch script that looks like this (DOS): @echo off rem Run Jython listening for debugger on port 8000 rem echo Args: %* dist\bin\jython -J-agentlib:jdwp=transport=dt_socket,server=y,address=8000,suspend=y %* where %* means "all the arguments to the batch file", so after building I type something like: > .\remote -m test.test_file_jy then in the IDE I connect to that port and we're off. Jeff Allen On 20/04/2018 01:31, Patrick Palczewski wrote: > > In IntelliJ, I can build using the build.xml with Ant, which enables > me to run Jython from the IDE or the command-line. > > However, if I want to debug a Jython java file (or run it), the IDE > insists on building the project and it will not compile, giving me > "Symbol not found" errors, though everything is in its proper place. > > I'm guessing thatI need to tweak intelliJ's build process and there > are specific switches that the Jython folks use to build Jython > without Ant and from the command-line. > > This will be a great help, and I can include it in my blog on setting > up IntelliJ for Jython development. > > Thanks. > > -- > /Patrick Palczewski/ *VRS# 818.208.2344* > |
|
From: Patrick Palczewski <psykiatris@gm...> - 2018-04-20 00:31:37
|
In IntelliJ, I can build using the build.xml with Ant, which enables me to run Jython from the IDE or the command-line. However, if I want to debug a Jython java file (or run it), the IDE insists on building the project and it will not compile, giving me "Symbol not found" errors, though everything is in its proper place. I'm guessing thatI need to tweak intelliJ's build process and there are specific switches that the Jython folks use to build Jython without Ant and from the command-line. This will be a great help, and I can include it in my blog on setting up IntelliJ for Jython development. Thanks. -- /Patrick Palczewski/ *VRS# 818.208.2344* |
|
From: Jeff Allen <ja.py@fa...> - 2018-04-15 17:06:14
|
In small steps on this, I have refactored PyJavaType.init from its original 560 lines to nearer 250 and a dozen helpers, with no change in meaning at this point. In the past, I have had to step through this code a lot and invariably I've lost my way. As I'll be doing more of that now, this ought to help. I can't say I understand everything it does yet (which makes sensible decisions more difficult). There is some helpful stuff around Java accessibility that I think I can adapt. Jeff Jeff Allen On 05/04/2018 21:28, Jeff Allen wrote: > Java 9 is throwing us an interesting problem. This will be an issue > wherever the factory pattern is used, and the actual class of object > handed out may be a private implementation class not exported to the > unnamed module. It's a common pattern. > > In Java, the compile-time type of the object is the public type the > factory method returns. The implementation type extends or implements > that "API" type, and it is the public methods of the API type that the > compiled code references. In Jython, we end up trying to reference the > implementation mthods directly. Java 9 forbids this, or at least > grumbles about it unattractively. > > I have an idea to resolve it, but it alters the Python type of a Java > class. Could be good or bad. What do others think? > > More in the text of the issue. http://bugs.jython.org/issue2662 > |
|
From: Jython tracker <status@bu...> - 2018-04-13 16:10:23
|
ACTIVITY SUMMARY (2018-04-06 - 2018-04-13) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 327 ( +3) closed 2360 ( +0) total 2687 ( +3) Open issues with patches: 28 Issues opened (3) ================= #2666: Imports in python from java do not work if there is a package http://bugs.jython.org/issue2666 opened by EhWhoAmI #2667: Virtualenv failed to create http://bugs.jython.org/issue2667 opened by MightyDash #2668: Thompson Kacis http://bugs.jython.org/issue2668 opened by nobody Most recent 15 issues with no replies (15) ========================================== #2668: Thompson Kacis http://bugs.jython.org/issue2668 #2666: Imports in python from java do not work if there is a package http://bugs.jython.org/issue2666 #2665: Standalone jar includes test classes http://bugs.jython.org/issue2665 #2663: Remove dependency on javax.xml.bind.DatatypeConverter http://bugs.jython.org/issue2663 #2651: Travis Builds failing with *** buffer overflow detected *** http://bugs.jython.org/issue2651 #2644: Representation of Java maps with String keys differs from Pyth http://bugs.jython.org/issue2644 #2640: Virtualenv gets confused using paths with ~ http://bugs.jython.org/issue2640 #2633: Unicode garbled in writing to spreadsheet via openpyxl http://bugs.jython.org/issue2633 #2631: jython 2.7.1 [Errno 107] Socket is not connected http://bugs.jython.org/issue2631 #2618: socket.sendall no longer sends all http://bugs.jython.org/issue2618 #2616: Incomplete / broken support for Certificate Revocation Lists http://bugs.jython.org/issue2616 #2605: Jython 2.7.0 startup performance regression http://bugs.jython.org/issue2605 #2591: Unable to execute directory or zip file (test_cmd_line_script) http://bugs.jython.org/issue2591 #2567: System state lost during JSR-223 initialisation http://bugs.jython.org/issue2567 #2562: Windows: OSError: unlink(): an unknown error occurred http://bugs.jython.org/issue2562 Most recent 15 issues waiting for review (15) ============================================= #2664: subprocess in jython ends with IOError: Stream closed http://bugs.jython.org/issue2664 #2635: AST.lineno ignored by compile http://bugs.jython.org/issue2635 #2566: inspect does not recognize code objects from bytecode files http://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules http://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the http://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses http://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline http://bugs.jython.org/issue2363 #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries http://bugs.jython.org/issue2121 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 Top 10 most discussed issues (2) ================================ #2664: subprocess in jython ends with IOError: Stream closed http://bugs.jython.org/issue2664 6 msgs #2410: Regression in PySystemStateTest (leading slash) http://bugs.jython.org/issue2410 3 msgs |
|
From: Rory O'Donnell <rory.odonnell@or...> - 2018-04-12 09:54:05
|
Hi Alan, **JDK 11 EA build 8, *****under both the GPL and Oracle EA licenses, is now available at **http://jdk.java.net/11**. ** * * Newly approved Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes * Summary of changes o https://download.java.net/java/early_access/jdk11/8/jdk-11+8.html *Notable changes in JDK 11 EA builds since last email:* * Build 8: o If you have a library that uses the Selector API heavily then now would be a good time to test it out. [1] * Build 7 o The VM option "-XX:+AggressiveOpts" is deprecated in JDK 11 and will be removed in a future release. * Build 6: o JDK-8193033 : remove terminally deprecated sun.misc.Unsafe.defineClass. Users should use the public replacement `java.lang.invoke.MethodHandles.Lookup.defineClass` which was added in Java SE 9. [2] ** *SURVEY: The HotSpot Serviceability Agent (SA) *[3] * If you have used, or have (support) processes that utilize the Serviceability Agent or related APIs, then we would definitely appreciate if you would complete this survey: https://www.surveymonkey.com/r/CF3MYDL Regards, Rory [1] http://mail.openjdk.java.net/pipermail/nio-dev/2018-April/004964.html [2] https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/MethodHandles.Lookup.html#defineClass-byte:A- [3] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001052.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland |
|
From: Jython tracker <status@bu...> - 2018-04-06 16:10:26
|
ACTIVITY SUMMARY (2018-03-30 - 2018-04-06) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 324 ( +3) closed 2360 ( +1) total 2684 ( +4) Open issues with patches: 26 Issues opened (4) ================= #2662: IllegalAccessException accessing public abstract method via Py http://bugs.jython.org/issue2662 opened by jeff.allen #2663: Remove dependency on javax.xml.bind.DatatypeConverter http://bugs.jython.org/issue2663 opened by jeff.allen #2664: subprocess in jython ends with http://bugs.jython.org/issue2664 opened by mga792 #2665: Standalone jar includes test classes http://bugs.jython.org/issue2665 opened by jeff.allen Most recent 15 issues with no replies (15) ========================================== #2665: Standalone jar includes test classes http://bugs.jython.org/issue2665 #2663: Remove dependency on javax.xml.bind.DatatypeConverter http://bugs.jython.org/issue2663 #2651: Travis Builds failing with *** buffer overflow detected *** http://bugs.jython.org/issue2651 #2644: Representation of Java maps with String keys differs from Pyth http://bugs.jython.org/issue2644 #2640: Virtualenv gets confused using paths with ~ http://bugs.jython.org/issue2640 #2633: Unicode garbled in writing to spreadsheet via openpyxl http://bugs.jython.org/issue2633 #2631: jython 2.7.1 [Errno 107] Socket is not connected http://bugs.jython.org/issue2631 #2618: socket.sendall no longer sends all http://bugs.jython.org/issue2618 #2616: Incomplete / broken support for Certificate Revocation Lists http://bugs.jython.org/issue2616 #2605: Jython 2.7.0 startup performance regression http://bugs.jython.org/issue2605 #2591: Unable to execute directory or zip file (test_cmd_line_script) http://bugs.jython.org/issue2591 #2567: System state lost during JSR-223 initialisation http://bugs.jython.org/issue2567 #2562: Windows: OSError: unlink(): an unknown error occurred http://bugs.jython.org/issue2562 #2531: Support SNI for SSL/TLS server sockets http://bugs.jython.org/issue2531 #2520: Jython does NOT support socket.listen(0) for accepting only on http://bugs.jython.org/issue2520 Most recent 15 issues waiting for review (15) ============================================= #2635: AST.lineno ignored by compile http://bugs.jython.org/issue2635 #2566: inspect does not recognize code objects from bytecode files http://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules http://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the http://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses http://bugs.jython.org/issue2367 #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries http://bugs.jython.org/issue2121 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 Top 10 most discussed issues (2) ================================ #2664: subprocess in jython ends with http://bugs.jython.org/issue2664 5 msgs #2363: relative seeks works incorrectly after readline http://bugs.jython.org/issue2363 4 msgs Issues closed (1) ================= #2661: New Inquiry Products (spam) http://bugs.jython.org/issue2661 closed by jeff.allen |
|
From: Jeff Allen <ja.py@fa...> - 2018-04-05 20:29:08
|
Java 9 is throwing us an interesting problem. This will be an issue wherever the factory pattern is used, and the actual class of object handed out may be a private implementation class not exported to the unnamed module. It's a common pattern. In Java, the compile-time type of the object is the public type the factory method returns. The implementation type extends or implements that "API" type, and it is the public methods of the API type that the compiled code references. In Jython, we end up trying to reference the implementation mthods directly. Java 9 forbids this, or at least grumbles about it unattractively. I have an idea to resolve it, but it alters the Python type of a Java class. Could be good or bad. What do others think? More in the text of the issue. http://bugs.jython.org/issue2662 -- Jeff Allen |
|
From: Jeff Allen <ja.py@fa...> - 2018-04-02 08:40:49
|
If you run Jython at the prompt with the --print option (using jython.py or jython.exe, or probably the shell script) it shows you the java command it would have used. Defaults -Xmx512m -Xss2560k shown are sufficient to run the regression tests, but of course there are no universally best values. I imagine the optimum under the IDE will be different from at the command line. Jeff Allen On 01/04/2018 18:56, Patrick Palczewski wrote: > > Jeff/Jim, > > I am in the process of documenting how to set up intelliJ to work with > Jython dev. The IDE has a default list of options for the VM in its > config file. Here are list of options: > > _________________ > > -Xms128m > -Xmx750m > -XX:ReservedCodeCacheSize=240m > -XX:+UseConcMarkSweepGC > -XX:SoftRefLRUPolicyMSPerMB=50 > -ea > -Dsun.io.useCanonCaches=false > -Djava.net.preferIPv4Stack=true > -XX:+HeapDumpOnOutOfMemoryError > -XX:-OmitStackTraceInFastThrow > -Dawt.useSystemAAFontSettings=lcd > -Dsun.java2d.renderer=sun.java2d.marlin.MarlinRenderingEngine > ____________ > > > Are there any VM settings I can add/change? I'm using IntelliJ 2018.1 > right now. > > -- > /Patrick Palczewski/ *VRS# 818.208.2344* > |
|
From: Jeff Allen <ja.py@fa...> - 2018-04-02 08:14:35
|
Patrick, that's really useful, thanks for taking the time to set it down
in a public place.
I think you have two potential audiences (may be 2 blogs).
1. I want to use Jython because I know Python but have a Java-only
environment, or Java libraries I can't do without.
2. I want to build Jython so I can hack on its internals, to
contribute, debug my own stuff, or just for study.
I think you've met the latter need well. Given the density of pictures,
the easiest thing would be to link it from the Dev Guide. I got as far
as raising an issue on our Dev Guide:
https://github.com/jython/devguide/issues/5
Although you say it should work for Windows, there can be a problem with
the jython.exe launcher (fixed in 2.7.2), at the point you use
jython.py, which is to do with some attempt Windows makes to share DLLs.
Although you suggest the choice of JVM version is minor, going beyond 8
is a problem we're working to fix.
It could do with a check for typos.
Jeff Allen
On 02/04/2018 05:02, Patrick Palczewski wrote:
>
> The following blog post demonstrates how to set up IntelliJ to work on
> gerneral Jython coding projects with steps on setting it to build and
> run run Jython itself from within the IDE.
>
> http://jythonblog.blogspot.com/2018/04/set-up-jython-projects-in-intellij-idea.html
>
> Comments and feedback welcome.
>
> --
> /Patrick Palczewski/ *VRS# 818.208.2344*
>
|
|
From: Patrick Palczewski <psykiatris@gm...> - 2018-04-02 04:02:12
|
The following blog post demonstrates how to set up IntelliJ to work on gerneral Jython coding projects with steps on setting it to build and run run Jython itself from within the IDE. http://jythonblog.blogspot.com/2018/04/set-up-jython-projects-in-intellij-idea.html Comments and feedback welcome. -- /Patrick Palczewski/ *VRS# 818.208.2344* |
|
From: Patrick Palczewski <psykiatris@gm...> - 2018-04-01 17:56:28
|
Jeff/Jim, I am in the process of documenting how to set up intelliJ to work with Jython dev. The IDE has a default list of options for the VM in its config file. Here are list of options: _________________ -Xms128m -Xmx750m -XX:ReservedCodeCacheSize=240m -XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 -ea -Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true -XX:+HeapDumpOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -Dawt.useSystemAAFontSettings=lcd -Dsun.java2d.renderer=sun.java2d.marlin.MarlinRenderingEngine ____________ Are there any VM settings I can add/change? I'm using IntelliJ 2018.1 right now. -- /Patrick Palczewski/ *VRS# 818.208.2344* |
|
From: Jeff Allen <ja.py@fa...> - 2018-04-01 12:07:54
|
One thing you could do to help would be to make a note (blog?) on how to set up IntelliJ to work with Jython ... assuming you succeeded. When I search for that, the top hit is a problem report (https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000459524-How-can-I-setup-Jython-in-IntelliJ-IDEA-Community-Edition-2017-2) which I have to admit is a thing I broke on Windows. (http://bugs.jython.org/issue2607) If you've set up IntelliJ so you can build Jython and fix bugs, I believe we have a place for you in the dev-guide, although I'm sure Jim would make useful additions. I think the first thing I did for the project was to update the notes on the Wiki on how to set up with Eclipse. That kind of information dates fairly quickly and what I found was out of date (as what I last wrote now is). I also have to build Jython outside the IDE when I want to be sure what I'm getting. (It depends a bit what the change is.) At the moment I'm debugging Java 9 behaviour, but I'm building with Java 7 as the lowest supported version and (sadly) the only one that builds smoothly for me. Jeff Jeff Allen On 11/03/2018 15:01, Patrick Palczewski wrote: > No, I didn't report it before as I didn't make a priority to focus on > it yet. > > I have been using intelliJ (and PyCham) for a few months. I saw the > issue at first when I triled to build from within the IDE. I didn't > worry about it as I could open a terminal and run ant from there. > > So, two days ago, I ran into the problem, and the hunt began. Now, I'm > happy as a clam, and using their built-in Ant makes it easy to switch > JDKs. > > I'm in the process of documenting how to set up IntelliJ for Jython > development with a note about using Ant from the IDE. > > Thanks, Jeff. you guys are great and I wish I could contribute. > > Patrick > > > > > On 03/11/2018 12:39 AM, Jeff Allen wrote: >> Good. It ought to work: I believe Jim B uses IntelliJ. >> >> I don't think we knew about this as an issue/post, did we? The only >> issue I can find with your name is http://bugs.jython.org/issue2649, >> which I think is still valid. >> >> Jeff Allen >> >> On 11/03/2018 02:13, Patrick Palczewski wrote: >>> >>> Hello, >>> >>> I successfully built a Jython project in IntelliJ configuring an Ant >>> build, using the existing build.xml. >>> >>> Tge nessages I was receiving were due to their Python plugin, which >>> uses a previous version of the JDK. >>> >>> Everythin's cool. >>> >>> -- >>> /Patrick Palczewski/ > > |
|
From: Jim Baker <jim.baker@py...> - 2018-03-31 23:07:51
|
Very much agreed with Jeff's summary. And this commitment to high quality with other fellow-minded contributors is what makes working on a project like CPython, Jython, or the Python standard library such a worthwhile longterm project for us. We figure out problems, write great code, and see what others have worked on in their solutions. This process does work, and it also allows us to contribute to this project as we have both time and insight. On Sat, Mar 31, 2018 at 11:17 AM, Jeff Allen <ja.py@...> wrote: > Those of us with commit rights help each other, and other contributors, > achieve adequate quality, I would say. If you're at the committing end of > this relationship, there is always the choice to be made between asking for > change and quietly improving a contribution. > > There is a coding standard, and that's useful, but I think coding > standards do not guarantee quality. So "compliance" is probably not the > right concept to apply, and it's more a matter of taste and experience, > which is not uniform. We're compliant in the other sense: willing to go > along with each other's criticism (mostly). For example, I've had to admit > at least once that I really should have written a test to go with my code, > when someone else gently pointed that out. In a dispute, I believe we'd all > give way to Frank and Jim as the longest-standing active contributors (and > Frank is the PM), although I've got away with disagreeing when my reasons > were good. > > This has worked without acrimony AFAIK during the time I've been > contributing to Jython. I think this is a Python tradition. I found > contributing to the main CPython dev-guide earlier this year to be an > exercise in humility at times, but it improved my work and wasn't a bad > experience overall. > > Jeff > > Jeff Allen > > On 30/03/2018 15:06, Patrick Palczewski wrote: > >> >> hello, >> >> I wanted to ask this question: Does Jython currently have someone who >> does compliance review, to reivew existing pr sib,submitted code to ensure >> it complys with Jython or Python guidelines? >> >> -- >> /Patrick Palczewski/ *VRS# 818.208.2344* >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jython-dev@... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Jeff Allen <ja.py@fa...> - 2018-03-31 17:55:48
|
Those of us with commit rights help each other, and other contributors, achieve adequate quality, I would say. If you're at the committing end of this relationship, there is always the choice to be made between asking for change and quietly improving a contribution. There is a coding standard, and that's useful, but I think coding standards do not guarantee quality. So "compliance" is probably not the right concept to apply, and it's more a matter of taste and experience, which is not uniform. We're compliant in the other sense: willing to go along with each other's criticism (mostly). For example, I've had to admit at least once that I really should have written a test to go with my code, when someone else gently pointed that out. In a dispute, I believe we'd all give way to Frank and Jim as the longest-standing active contributors (and Frank is the PM), although I've got away with disagreeing when my reasons were good. This has worked without acrimony AFAIK during the time I've been contributing to Jython. I think this is a Python tradition. I found contributing to the main CPython dev-guide earlier this year to be an exercise in humility at times, but it improved my work and wasn't a bad experience overall. Jeff Jeff Allen On 30/03/2018 15:06, Patrick Palczewski wrote: > > hello, > > I wanted to ask this question: Does Jython currently have someone who > does compliance review, to reivew existing pr sib,submitted code to > ensure it complys with Jython or Python guidelines? > > -- > /Patrick Palczewski/ *VRS# 818.208.2344* > |
|
From: Jython tracker <status@bu...> - 2018-03-30 16:10:27
|
ACTIVITY SUMMARY (2018-03-23 - 2018-03-30) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 321 ( +3) closed 2359 ( +1) total 2680 ( +4) Open issues with patches: 26 Issues opened (4) ================= #2658: Update jython.org website http://bugs.jython.org/issue2658 opened by jeff.allen #2659: Determine console encoding without access violation (Java 9) http://bugs.jython.org/issue2659 opened by jeff.allen #2660: Failure in urllib3 using versions of pip after pip 9.0.1 http://bugs.jython.org/issue2660 opened by jeff.allen #2661: New Inquiry Products http://bugs.jython.org/issue2661 opened by nobody Most recent 15 issues with no replies (15) ========================================== #2661: New Inquiry Products http://bugs.jython.org/issue2661 #2660: Failure in urllib3 using versions of pip after pip 9.0.1 http://bugs.jython.org/issue2660 #2658: Update jython.org website http://bugs.jython.org/issue2658 #2651: Travis Builds failing with *** buffer overflow detected *** http://bugs.jython.org/issue2651 #2644: Representation of Java maps with String keys differs from Pyth http://bugs.jython.org/issue2644 #2640: Virtualenv gets confused using paths with ~ http://bugs.jython.org/issue2640 #2633: Unicode garbled in writing to spreadsheet via openpyxl http://bugs.jython.org/issue2633 #2631: jython 2.7.1 [Errno 107] Socket is not connected http://bugs.jython.org/issue2631 #2618: socket.sendall no longer sends all http://bugs.jython.org/issue2618 #2616: Incomplete / broken support for Certificate Revocation Lists http://bugs.jython.org/issue2616 #2605: Jython 2.7.0 startup performance regression http://bugs.jython.org/issue2605 #2591: Unable to execute directory or zip file (test_cmd_line_script) http://bugs.jython.org/issue2591 #2567: System state lost during JSR-223 initialisation http://bugs.jython.org/issue2567 #2562: Windows: OSError: unlink(): an unknown error occurred http://bugs.jython.org/issue2562 #2531: Support SNI for SSL/TLS server sockets http://bugs.jython.org/issue2531 Most recent 15 issues waiting for review (15) ============================================= #2635: AST.lineno ignored by compile http://bugs.jython.org/issue2635 #2566: inspect does not recognize code objects from bytecode files http://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules http://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the http://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses http://bugs.jython.org/issue2367 #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries http://bugs.jython.org/issue2121 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 Top 10 most discussed issues (1) ================================ #2659: Determine console encoding without access violation (Java 9) http://bugs.jython.org/issue2659 3 msgs Issues closed (1) ================= #2055: isinstance() and issubclass() fail with abc.ABCMeta http://bugs.jython.org/issue2055 closed by jeff.allen |
|
From: Patrick Palczewski <psykiatris@gm...> - 2018-03-30 14:06:25
|
hello, I wanted to ask this question: Does Jython currently have someone who does compliance review, to reivew existing pr sib,submitted code to ensure it complys with Jython or Python guidelines? -- /Patrick Palczewski/ *VRS# 818.208.2344* |
|
From: Oti <ohumbel@gm...> - 2018-03-27 21:35:05
|
Hi Jeff, I have been playing with the replacement of the disallowed call during my snowboard holidays. Since java.io.Console.encoding() returns null on all platforms except Windows, it was almost a no-brainer to simplify it (except for Windows). Please find all the details behind http://bugs.jython.org/issue2659. best wishes, Oti. On Tue, Mar 27, 2018 at 12:14 AM, Jeff Allen <ja.py@...> wrote: > When nothing else tells us the console encoding, we obtain it by a > reflective call to the private java.io.Console.encoding(), which Java 9 > doesn't like and threatens to disallow. I propose re-thinking this to avoid > the call. > > See http://bugs.jython.org/issue2659 for a first idea. > > Jeff > -- > > Jeff Allen > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jython-dev@... > https://lists.sourceforge.net/lists/listinfo/jython-dev > -- http://ohumbel.me |
|
From: Jeff Allen <ja.py@fa...> - 2018-03-26 22:14:39
|
When nothing else tells us the console encoding, we obtain it by a reflective call to the private java.io.Console.encoding(), which Java 9 doesn't like and threatens to disallow. I propose re-thinking this to avoid the call. See http://bugs.jython.org/issue2659 for a first idea. Jeff -- Jeff Allen |
|
From: <fwierzbicki@gm...> - 2018-03-26 15:01:26
|
On Sat, Mar 24, 2018 at 3:58 AM, Jeff Allen <ja.py@...> wrote: > I have read every open issue now on bugs.jython.org, understood the vast > majority, commented on many of them, and investigated a few in depth. If it > seemed to be invalid or fixed, I closed it or made it pending > fixed/invalid/etc.. > Thanks for all of that work! > I use "pending" to mean "probably, but let's see what anyone else or > experience tells us". 295 are open, 22 are "pending". > > In a massive cull, I have taken the 2.7.2 milestone off all but 15. These > are in the following categories: > > Obstacle to running Jython on Java 9. (We can't ignore that any longer, > surely?) > Obstacle to using with Gradle. (I need to understand it better -- or someone > else does.) > Actually or nearly resolved (significant recent progress, patch or just > waiting confirmation fixed). > Web site update (possible 16th issue to cover). Depending on the timeline I may be able to help on the web site, since I've moved the website a few times before. > > I have not done a comparable sweep of GitHub on the assumption that anything > vital has a counterpart on the official tracker. > > I think we should shy away from risky change on the trunk once we tag a beta > version (April sometime?). I have not assigned anything to milestone 2.7.3 > because there isn't one (!) and I think we should do so at this stage only > if we feel really strongly and are comfortable about our capacity. Better > not to raise hopes than to dash them later. Agreed! I can add milestones whenever we need them. If you do want the 2.7.3 let me know. > Reading the issues was interesting, but having to keep reading instead of > fixing them was frustrating, so I'm looking forward to doing some of that. > Easter is coming, which will give me a few extra days. Anyone else able to > give 2.7.2 a bit of a push? I think I have some time during the Easter break to at least do some planning on the website move. I'll also have a look at the tracker tickets. Thanks! -Frank |
|
From: Jim Baker <jim.baker@py...> - 2018-03-25 16:02:11
|
On Sat, Mar 24, 2018 at 4:58 AM, Jeff Allen <ja.py@...> wrote: > I have read every open issue now on bugs.jython.org, understood the vast > majority, commented on many of them, and investigated a few in depth. If it > seemed to be invalid or fixed, I closed it or made it pending > fixed/invalid/etc.. > Wow, that's an impressive amount of work to triage all these bugs! > I use "pending" to mean "probably, but let's see what anyone else or > experience tells us". 295 are open, 22 are "pending". > > In a massive cull, I have taken the 2.7.2 milestone off all but 15. These > are in the following categories: > > 1. Obstacle to running Jython on Java 9. (We can't ignore that any > longer, surely?) > > Agreed, especially with the recent Java 10 GA. But presumably the same issues apply for Java 10. The key piece here will be able to replicate what we do with package scanning and private access. I believe there are solutions for each. IDEs obviously have to do something like package scanning; and private access has some options http://in.relation.to/2017/04/11/accessing-private-state-of-java-9-modules/ > > 1. Obstacle to using with Gradle. (I need to understand it better -- > or someone else does.) > > re http://bugs.jython.org/issue2182 - the reasoning for this is we want to move out of having binaries mixed with the source code tree; and make it easier for people to reuse Jython in contemporary builds so they can pull only our code into it and not have all of this extra crud with respect to re-namedspaced jars. But I don't see this as a blocker for 2.7.2 > > 1. Actually or nearly resolved (significant recent progress, patch or > just waiting confirmation fixed). > > I would need to go through 15 of these issues, plus the 22 pending. But for example http://bugs.jython.org/issue2230 1) we didn't get a response from the OP; 2) Jeff's work here fixed what has to be the same bug from our informed perspective. From a triage perspective, we have to call this fixed. In the past I would mark this as "pending" for a week or two, then move to fixed just to signal this to the community. > > 1. Web site update (possible 16th issue to cover). > > I would see this as the most important thing to do for the 2.7.2 release. Of course we all love writing documentation :), but here's it's more of a question of editing what we have in a more current format. So moving to Read to the Docs seems like the best approach here. There is plenty of room to disagree about the choice. Also, *not* assigning > to 2.7.2 is not a prohibition on contributing something you fancy doing. I > assigned myself some I liked but don't think are 2.7.2 blockers. > Unfortunately, the first two could be complicated. As mentioned before, > sockets & SSL is a recurring theme. I've not made any of those blockers, > but it's the area where I feel it is most likely I am overlooking the > importance of one or more issues. > I'm very skeptical of sockets/SSL blocking 2.7.2. This work proved to work better than I ever expected for server usage; and yet because of that we worked harder to make it even more compatible. But the reality is that we should expect most server usage of socket code would use other Java containers, whether they are a servlet container like Jetty or something built directly on Netty. > I have not done a comparable sweep of GitHub on the assumption that > anything vital has a counterpart on the official tracker. > Sounds reasonable. > I think we should shy away from risky change on the trunk once we tag a > beta version (April sometime?). I have not assigned anything to milestone > 2.7.3 because there isn't one (!) and I think we should do so at this stage > only if we feel really strongly and are comfortable about our capacity. > Better not to raise hopes than to dash them later. > Yes, this is very important! > Reading the issues was interesting, but having to keep reading instead of > fixing them was frustrating, so I'm looking forward to doing some of that. > Easter is coming, which will give me a few extra days. Anyone else able to > give 2.7.2 a bit of a push? > I'm personally very limited in what I can do until this summer at the earliest. Maybe I can help on some of the doc stuff after Easter, but I don't want to be on any critical path. But I do plan to be at EuroPython in Edinburgh, since I will be nearby at that time in the UK for work reasons. - Jim On 05/03/2018 09:26, Jim Baker wrote: > > Jeff, > > This makes sense to remove tags. Certainly there was optimistic estimation > of available resources on my part, based on what I was then doing — I went > from 50% (or more) availability 3 years ago, then 20% 2 years ago but > combined with a heavy part-time teaching load, to basically none at this > moment. (But I hope to have some chance to contribute by this summer!) > > We have a lot of great work in 2.7.2, so it's important to get this out. > My basic feeling is that the web site cleanup, especially moving to some > sort of ReadTheDocs approach, is the big thing that needs to be done. Most > likely everything else outstanding can go into a later release. > > - Jim > > > On Fri, Mar 2, 2018 at 9:14 AM, Jeff Allen <ja.py@...> wrote: > >> I'm continuing the triage of issues, slowly. Given our rate of work and >> jointly-expressed desire for a release, I find the only rational course is >> to take off nearly all the 2.7.2 tags, unless it would be harmful to >> release with that issue. (I might add some on that basis.) I'll do my best >> to follow the comments on each issue first. >> >> I'll get this wrong many times, so if I've taken 2.7.2 off where you can >> see Jython wouldn't be viable with that issue outstanding, please argue it >> on the issue. Also, a good patch or commit is close to an irrefutable >> argument for inclusion. Anyone is free to to fix something just because >> they think it worthwhile or fun to do: we're all volunteers. >> >> That said, we have a fair number of issues related to sockets/SSL that I >> find difficult to assess accurately and could not easily work on. If your >> skills and interest run that way, they might be good choices. >> >> Some projects tag issues as "suitable for beginners". We don't have such >> a tag, but as I go through the issues, I find Jim has often done the like >> in a comment or given a hint towards the likely solution, which is useful >> for the rest of us. >> >> Other thoughts in line ... >> >> Jeff >> >> On 26/02/2018 03:00, fwierzbicki@... wrote: >> >>> Hi Jeff - some comments inline: >>> >>> On Sun, Feb 25, 2018 at 12:49 AM, Jeff Allen <ja.py@...> wrote: >>> >>>> It's still the New Year :) >>>> >>>> We currently have 85 open bugs tagged Milestone 2.7.2, and about 250 >>>> others. >>>> (20 or so are tagged 2.7.1 or 2.7.0, but I think that's mostly a >>>> misunderstanding at the time they were raised.) It's hard for me to say >>>> which should be show-stoppers. >>>> >>>> I thought I'd at least read them all. So far I've got 2 categories: >>>> "fairly >>>> sure I can close" and "that's not simple". >>>> >>>> I think we should have tagged as Milestone 2.7.2 only those things we >>>> have a >>>> serious intention to fix by the end of 2.7.2b, and everything else >>>> decisively put off. Knowledgeable contributions to this process would be >>>> welcome. >>>> >>> That sounds right to me, we can put others into a 2.7.3 Milestone >>> perhaps. >>> >> No milestones are available for selection in the tracker beyond 2.7.2, so >> we can't express that idea at present. Also, I think it means very little >> to add 2.7.3 until we start to plan it. Anything not tagged is a candidate >> for 2.7.3 according to priority (or fancy). Priority and severity are >> useful at all times, I think. >> >> A 2.7.3 milestone could be in the database ready, however. Oddly, I can >> report an error against 2.7.3 if I want, but not against 2.7.2. >> >> I think (below) Frank bids a GitHub-based website as part of the 2.7.2, >>>> which I think is highly desirable for communication reasons. >>>> >>> Yes I need to look at the logistics of getting a github based website >>> up and running. I'll try to find some time to look into that soonish. >>> >> That would be great. And we need the basic content, of course, before >> throwing the switch. I'm going to focus on the issues triage. >> >> Jeff >> >> > > |
|
From: Jeff Allen <ja.py@fa...> - 2018-03-24 10:58:10
|
I have read every open issue now on bugs.jython.org, understood the vast
majority, commented on many of them, and investigated a few in depth. If
it seemed to be invalid or fixed, I closed it or made it pending
fixed/invalid/etc..
I use "pending" to mean "probably, but let's see what anyone else or
experience tells us". 295 are open, 22 are "pending".
In a massive cull, I have taken the 2.7.2 milestone off all but 15.
These are in the following categories:
1. Obstacle to running Jython on Java 9. (We can't ignore that any
longer, surely?)
2. Obstacle to using with Gradle. (I need to understand it better -- or
someone else does.)
3. Actually or nearly resolved (significant recent progress, patch or
just waiting confirmation fixed).
4. Web site update (possible 16th issue to cover).
There is plenty of room to disagree about the choice. Also, *not*
assigning to 2.7.2 is not a prohibition on contributing something you
fancy doing. I assigned myself some I liked but don't think are 2.7.2
blockers. Unfortunately, the first two could be complicated. As
mentioned before, sockets & SSL is a recurring theme. I've not made any
of those blockers, but it's the area where I feel it is most likely I am
overlooking the importance of one or more issues.
I have not done a comparable sweep of GitHub on the assumption that
anything vital has a counterpart on the official tracker.
I think we should shy away from risky change on the trunk once we tag a
beta version (April sometime?). I have not assigned anything to
milestone 2.7.3 because there isn't one (!) and I think we should do so
at this stage only if we feel really strongly and are comfortable about
our capacity. Better not to raise hopes than to dash them later.
Reading the issues was interesting, but having to keep reading instead
of fixing them was frustrating, so I'm looking forward to doing some of
that. Easter is coming, which will give me a few extra days. Anyone else
able to give 2.7.2 a bit of a push?
Jeff
Jeff Allen
On 05/03/2018 09:26, Jim Baker wrote:
> Jeff,
>
> This makes sense to remove tags. Certainly there was optimistic
> estimation of available resources on my part, based on what I was then
> doing — I went from 50% (or more) availability 3 years ago, then 20% 2
> years ago but combined with a heavy part-time teaching load, to
> basically none at this moment. (But I hope to have some chance to
> contribute by this summer!)
>
> We have a lot of great work in 2.7.2, so it's important to get this
> out. My basic feeling is that the web site cleanup, especially moving
> to some sort of ReadTheDocs approach, is the big thing that needs to
> be done. Most likely everything else outstanding can go into a later
> release.
>
> - Jim
>
>
> On Fri, Mar 2, 2018 at 9:14 AM, Jeff Allen <ja.py@...
> <mailto:ja.py@...>> wrote:
>
> I'm continuing the triage of issues, slowly. Given our rate of
> work and jointly-expressed desire for a release, I find the only
> rational course is to take off nearly all the 2.7.2 tags, unless
> it would be harmful to release with that issue. (I might add some
> on that basis.) I'll do my best to follow the comments on each
> issue first.
>
> I'll get this wrong many times, so if I've taken 2.7.2 off where
> you can see Jython wouldn't be viable with that issue outstanding,
> please argue it on the issue. Also, a good patch or commit is
> close to an irrefutable argument for inclusion. Anyone is free to
> to fix something just because they think it worthwhile or fun to
> do: we're all volunteers.
>
> That said, we have a fair number of issues related to sockets/SSL
> that I find difficult to assess accurately and could not easily
> work on. If your skills and interest run that way, they might be
> good choices.
>
> Some projects tag issues as "suitable for beginners". We don't
> have such a tag, but as I go through the issues, I find Jim has
> often done the like in a comment or given a hint towards the
> likely solution, which is useful for the rest of us.
>
> Other thoughts in line ...
>
> Jeff
>
> On 26/02/2018 03:00, fwierzbicki@...
> <mailto:fwierzbicki@...> wrote:
>
> Hi Jeff - some comments inline:
>
> On Sun, Feb 25, 2018 at 12:49 AM, Jeff Allen
> <ja.py@... <mailto:ja.py@...>> wrote:
>
> It's still the New Year :)
>
> We currently have 85 open bugs tagged Milestone 2.7.2, and
> about 250 others.
> (20 or so are tagged 2.7.1 or 2.7.0, but I think that's
> mostly a
> misunderstanding at the time they were raised.) It's hard
> for me to say
> which should be show-stoppers.
>
> I thought I'd at least read them all. So far I've got 2
> categories: "fairly
> sure I can close" and "that's not simple".
>
> I think we should have tagged as Milestone 2.7.2 only
> those things we have a
> serious intention to fix by the end of 2.7.2b, and
> everything else
> decisively put off. Knowledgeable contributions to this
> process would be
> welcome.
>
> That sounds right to me, we can put others into a 2.7.3
> Milestone perhaps.
>
> No milestones are available for selection in the tracker beyond
> 2.7.2, so we can't express that idea at present. Also, I think it
> means very little to add 2.7.3 until we start to plan it. Anything
> not tagged is a candidate for 2.7.3 according to priority (or
> fancy). Priority and severity are useful at all times, I think.
>
> A 2.7.3 milestone could be in the database ready, however. Oddly,
> I can report an error against 2.7.3 if I want, but not against 2.7.2.
>
> I think (below) Frank bids a GitHub-based website as part
> of the 2.7.2,
> which I think is highly desirable for communication reasons.
>
> Yes I need to look at the logistics of getting a github based
> website
> up and running. I'll try to find some time to look into that
> soonish.
>
> That would be great. And we need the basic content, of course,
> before throwing the switch. I'm going to focus on the issues triage.
>
> Jeff
>
>
|
|
From: Jython tracker <status@bu...> - 2018-03-23 17:10:22
|
ACTIVITY SUMMARY (2018-03-16 - 2018-03-23) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 318 ( -5) closed 2358 ( +5) total 2676 ( +0) Open issues with patches: 26 Most recent 15 issues with no replies (15) ========================================== #2651: Travis Builds failing with *** buffer overflow detected *** http://bugs.jython.org/issue2651 #2644: Representation of Java maps with String keys differs from Pyth http://bugs.jython.org/issue2644 #2640: Virtualenv gets confused using paths with ~ http://bugs.jython.org/issue2640 #2633: Unicode garbled in writing to spreadsheet via openpyxl http://bugs.jython.org/issue2633 #2631: jython 2.7.1 [Errno 107] Socket is not connected http://bugs.jython.org/issue2631 #2618: socket.sendall no longer sends all http://bugs.jython.org/issue2618 #2616: Incomplete / broken support for Certificate Revocation Lists http://bugs.jython.org/issue2616 #2605: Jython 2.7.0 startup performance regression http://bugs.jython.org/issue2605 #2591: Unable to execute directory or zip file (test_cmd_line_script) http://bugs.jython.org/issue2591 #2567: System state lost during JSR-223 initialisation http://bugs.jython.org/issue2567 #2562: Windows: OSError: unlink(): an unknown error occurred http://bugs.jython.org/issue2562 #2531: Support SNI for SSL/TLS server sockets http://bugs.jython.org/issue2531 #2520: Jython does NOT support socket.listen(0) for accepting only on http://bugs.jython.org/issue2520 #2482: Publish U.S. ECCN for Jython http://bugs.jython.org/issue2482 #2410: Regression in PySystemStateTest (leading slash) http://bugs.jython.org/issue2410 Most recent 15 issues waiting for review (15) ============================================= #2635: AST.lineno ignored by compile http://bugs.jython.org/issue2635 #2566: inspect does not recognize code objects from bytecode files http://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules http://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the http://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses http://bugs.jython.org/issue2367 #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries http://bugs.jython.org/issue2121 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 Issues closed (4) ================= #1742: Finders in sys.meta_path do not work for Java modules in packa http://bugs.jython.org/issue1742 closed by jeff.allen #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 closed by jeff.allen #1930: traceback raises exception in os.py http://bugs.jython.org/issue1930 closed by jeff.allen #610966: Improving doc about applet issues http://bugs.jython.org/issue610966 closed by jeff.allen |
|
From: Jeff Allen <ja.py@fa...> - 2018-03-21 22:39:21
|
A lot of our open issues mention jyjdbc as the silver bullet solution (maybe 3.5 years ago). Is this still what we intend? Not for 2.7.2 I would guess. But a nice piece of work if it closes a dozen or so bugs. -- Jeff Allen |
|
From: Rory O'Donnell <rory.odonnell@or...> - 2018-03-21 10:59:43
|
Hi Alan, A number of items to share with you today : *1) JDK 10 General Availability * JDK 10, the first release produced under the six-month rapid-cadence release model [1][2], is now Generally Available. We've identified no P1 bugs since we promoted build 46 almost two weeks ago, so that is the official GA release, ready for production use. GPL'd binaries from Oracle are available here: http://jdk.java.net/10 This release includes twelve features: * 286: Local-Variable Type Inference <http://openjdk.java.net/jeps/286>; * 296: Consolidate the JDK Forest into a Single Repository <http://openjdk.java.net/jeps/296>; * 304: Garbage-Collector Interface <http://openjdk.java.net/jeps/304>; * 307: Parallel Full GC for G1 <http://openjdk.java.net/jeps/307>; * 310: Application Class-Data Sharing <http://openjdk.java.net/jeps/310>; * 312: Thread-Local Handshakes <http://openjdk.java.net/jeps/312>; * 313: Remove the Native-Header Generation Tool (javah) <http://openjdk.java.net/jeps/313>; * 314: Additional Unicode Language-Tag Extensions <http://openjdk.java.net/jeps/314>; * 316: Heap Allocation on Alternative Memory Devices <http://openjdk.java.net/jeps/316>; * 317: Experimental Java-Based JIT Compiler <http://openjdk.java.net/jeps/317>; * 319: Root Certificates <http://openjdk.java.net/jeps/319>; * 322: Time-Based Release Versioning <http://openjdk.java.net/jeps/322>; *2) JDK 11 EA build 5, under both the GPL and Oracle EA licenses, are now available at **http://jdk.java.net/11**.* * Schedule, status & features o http://openjdk.java.net/projects/jdk/11/ * Release Notes: o http://jdk.java.net/11/release-notes * Summary of changes o https://download.java.net/java/early_access/jdk11/5/jdk-11+5.html *3) The Z Garbage Collector Project, early access builds available : * The first EA binary from from The Z Garbage Collector Project, also known as ZGC, is now available. ZGC is a scalable low latency garbage collector. For information on how to enable and use ZGC, please see the project wiki. * Project page: http://openjdk.java.net/projects/zgc/ * Wiki: https://wiki.openjdk.java.net/display/zgc/Main *4) Quality Outreach Report for **March 2018 **is available * * https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+March+2018 *5) **Java Client Roadmap Update * * We posted a blog [3] and related white paper [4] detailing our plans for the Java Client. Rgds,Rory [1] https://mreinhold.org/blog/forward-faster [2] http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html [3] Blog: https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates [4] Whitepaper: http://www.oracle.com/technetwork/java/javase/javaclientroadmapupdate2018mar-4414431.pdf -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland |
|
From: Jeff Allen <ja.py@fa...> - 2018-03-19 22:11:59
|
On 19/03/2018 11:32, Eero Aaltonen wrote: > > Hi Jeff, > > Having just read this, a potential counterexample came to my mind. > > Suppose we want to pass a PyObject Pyo from PyInterpreterState PySa to > PyInterpreterState PySb. I'm not familiar with Jythons internals, but > I would assume many of the things that apply to passing object between > classloaders would apply here as well. > If the Pyo was loaded in a common classloader, the module of Pyo would > likely be loaded by that common classloader and the module would then > be unusable for distinguishing PySa and PySb. > > Disclaimer: This is with very limited knowledge of Jython. > > -- > Eero Aaltonen Too great a knowledge of actual Jython internals may be a disadvantage. Mine is helpfully blurred. Thanks for thinking about this. A module source compiles to a Java class (or CPython PyCode) but the object in sys.modules is a PyModule instance which references the compiled class, and I suggest could contain a reference to an importing interpreter. The compiled module is a constant, while the PyModule contains the variable state (per interpreter I propose). We would use the reference upon entry to Python-aware code in that module to find the right sys module, codec registry, etc. and PyThread. In Jython there is a call to ThreadStateMapping.getThreadState and later ThreadStateMapping.enterCall and although that is mechanism I'm questioning, it is around there that this would happen. It cannot *I think* depend on class loader identity, but needs a specific reference. I didn't mention the important matter of class loaders because I don't quite know what I think about them. It seems likely that module finders/loaders are the Python idea that corresponds most closely to a Java class loader, in the same way that the Python and JVM threads correspond (but are not the same). It might be that each finder references a class loader. And of course each interpreter has its own sequence of finders, including a default one whose class loader might be the one that loaded the interpreter class of which it is an instance. There is at least some coherency required between interpreters and class loaders, so that two applications using Jython in the same JVM work without interference. Jeff |