Menu
▾
▴
jython-dev — Discussion of developing and enhancing Jython itself(!) (not how to use Jython)
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
(19) |
May
(14) |
Jun
(9) |
Jul
(9) |
Aug
(22) |
Sep
(22) |
Oct
(12) |
Nov
(13) |
Dec
(8) |
| 2019 |
Jan
(22) |
Feb
(3) |
Mar
(30) |
Apr
(20) |
May
(20) |
Jun
(6) |
Jul
(15) |
Aug
(25) |
Sep
(11) |
Oct
(24) |
Nov
(11) |
Dec
(6) |
| 2020 |
Jan
(9) |
Feb
(12) |
Mar
(29) |
Apr
(10) |
May
(22) |
Jun
(11) |
Jul
(15) |
Aug
(5) |
Sep
(6) |
Oct
(7) |
Nov
(7) |
Dec
(13) |
| 2021 |
Jan
(21) |
Feb
(5) |
Mar
(5) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(6) |
Aug
(8) |
Sep
(5) |
Oct
(9) |
Nov
(5) |
Dec
(6) |
| 2022 |
Jan
(5) |
Feb
(4) |
Mar
(8) |
Apr
(6) |
May
(5) |
Jun
(5) |
Jul
(10) |
Aug
(6) |
Sep
(7) |
Oct
(4) |
Nov
(4) |
Dec
(6) |
| 2023 |
Jan
(5) |
Feb
(5) |
Mar
(6) |
Apr
(4) |
May
(5) |
Jun
(6) |
Jul
(5) |
Aug
(5) |
Sep
(5) |
Oct
(5) |
Nov
(7) |
Dec
(8) |
| 2024 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pekka K. <pe...@ik...> - 2019-11-21 22:06:00
|
Hi Jeff and rest of the Jython crew! I tested Jython Jython 2.7.2 beta 2 by running Robot Framework projects (github.com/robotframework/robotframework) comprehensive acceptance test set with it both on Linux and Windows without major issues. The only regressions I found I were https://bugs.jython.org/issue2820 and https://bugs.jython.org/issue2824. Neither of them are showstoppers for us and I can just disable related tests with Jython if they aren't fixed. Do you have any timeline when Jython 2.7.2 final would be released? We are currently working with Robot Framework 3.2 with a target to get it out still this year. One of our distributions is robotframework.jar with embedded Jython, and if possible I'd like to updated Jython it contains to 2.7.2. Once Jython 2.7.2 is out, I hope development effort would be targeted for Jython 3. The main reason we aren't planning to drop Python 2 support yet is to support Jython, but I doubt we want to write or even maintain Python 2 code anymore in 2021. Thanks for your work and the new release! Cheers, .peke pe 1. marrask. 2019 klo 23.02 Jeff Allen (ja...@fa...) kirjoitti: > > We're there ... Jython 2.7.2b2 is at long last live. (There never was a public 2.7.2b1.) Find it here: > > jython-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython/2.7.2b2/) > jython-installer-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython-installer/2.7.2b2/) > jython-slim-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython-slim/2.7.2b2/) > jython-standalone-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython-standalone/2.7.2b2/) > > As I write, these are not yet showing on https://search.maven.org/search?q=g:org.python but I assume it will catch up eventually. Maven and Gradle builds on my local machine already download jython-slim named as a dependency. > > Heartfelt thanks go to all who've contributed to this release. Now let's find out what the users make of it. > > Jeff > > Frank: > > could you do the bits only you know how, please? On the bug-tracker can you make it possible to raise bugs against 2.7.1 and 2.7.2, and to have milestones 2.7.3 and 2.7.4 ? > > Jeff > > -- > Jeff Allen > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev -- Agile Tester/Developer/Consultant :: http://eliga.fi Lead Developer of Robot Framework :: http://robotframework.org |
|
From: Jython t. <st...@bu...> - 2019-11-15 18:05:37
|
ACTIVITY SUMMARY (2019-11-08 - 2019-11-15) Jython tracker at https://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 335 ( +1) closed 2461 ( +0) total 2796 ( +1) Open issues with patches: 23 Issues opened (1) ================= #2830: Unable to run Jython on Windows Server 2008 R2 https://bugs.jython.org/issue2830 opened by marcuswongkl Most recent 15 issues with no replies (15) ========================================== #2828: Upgrade netty from 4.1.24 https://bugs.jython.org/issue2828 #2826: Unicode hex string decode fails with Jython 2.7.2.b3 https://bugs.jython.org/issue2826 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2792: Failures in test_import_jy from Java 13 https://bugs.jython.org/issue2792 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 #2770: PBKDF-OpenSSL SecretKeyFactory not available on Java 7 https://bugs.jython.org/issue2770 #2760: How to call procedure with use zxjdbc and get back OUT paramet https://bugs.jython.org/issue2760 #2754: Failure in Py.initProxy for class not at module level https://bugs.jython.org/issue2754 #2752: Allow Python functions to be used as a java.lang.FunctionalInt https://bugs.jython.org/issue2752 #2750: Make PyFunction implement java.util.concurrent.Callable<PyObje https://bugs.jython.org/issue2750 #2734: Re-work package scanning and cache for modules https://bugs.jython.org/issue2734 #2723: Unusual behavior in SimpleCookie when '=' and '@' is used in https://bugs.jython.org/issue2723 #2722: run-time issue while trying to reach external endpoint (Weathe https://bugs.jython.org/issue2722 #2720: wrap_scoket_exception: 'module' object has no attribute 'OP_NO https://bugs.jython.org/issue2720 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2230: Jython evaluation blocks under heavy load with high multi-core https://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 |
|
From: Rory O'D. <ror...@or...> - 2019-11-12 09:45:01
|
Hi Alan, *OpenJDK builds - JDK 14 *- Early Access build 22 is available at http://jdk.java.net/14/ These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release notes o https://jdk.java.net/14/release-notes * JEPs targeted to JDK 14, so far: * JEP 345: NUMA-Aware Memory Allocation for G1 <http://openjdk.java.net/jeps/345> was Targeted to JDK 14. * JEP 349: JFR Event Streaming <http://openjdk.java.net/jeps/349> was Integrated. * JEP 361: Switch Expressions (Standard) <http://openjdk.java.net/jeps/361> was Targeted to JDK 14. * JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector <http://openjdk.java.net/jeps/363> was Targeted to JDK 14. * JEP 364: ZGC on macOS <http://openjdk.java.net/jeps/364> was Targeted to JDK 14. * JEP 365: ZGC on Windows <http://openjdk.java.net/jeps/365> moved to Candidate. * JEP 366: Deprecate the ParallelScavenge + SerialOld GC Combination <http://openjdk.java.net/jeps/366> was Proposed to target JDK 14. * JEP 367: Remove the Pack200 Tools and API <http://openjdk.java.net/jeps/367> was Targeted to JDK 14. * JEP 368: Text Blocks (Second Preview) <http://openjdk.java.net/jeps/368> moved to Candidate. * Changes in this build <http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B21%22%3A%3A%22jdk-14%2B22%22-%22jdk-14%2B21%22%29&revcount=1000> *jpackage EA -* Build 14-jpackage+1-67 (2019/11/4) * This is an early access build of JEP 343: Packaging Tool <https://openjdk.java.net/jeps/343>, aimed at testing a prototype implementation of jpackage, which is a new tool for packaging self-contained Java applications along with a Java Runtime Environment. * These early-access builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html> * Build 14 is now available http://jdk.java.net/jpackage/ * Please send feedback via e-mail to cor...@op... <mailto:cor...@op...> -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland |
|
From: Jython t. <st...@bu...> - 2019-11-08 18:05:39
|
ACTIVITY SUMMARY (2019-11-01 - 2019-11-08) Jython tracker at https://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 334 (-11) closed 2461 (+16) total 2795 ( +5) Open issues with patches: 23 Issues opened (6) ================= #2044: Jython creates executables class files with wrong permissions https://bugs.jython.org/issue2044 reopened by jeff.allen #2820: Importing non-existing module fails with UnicodeDecodeError if https://bugs.jython.org/issue2820 opened by pekka.klarck #2822: Add support for Java 11 https://bugs.jython.org/issue2822 opened by respenica #2824: `os.path.abspath()` doesn't add drive letter to absolute paths https://bugs.jython.org/issue2824 opened by pekka.klarck #2826: Unicode hex string decode fails with Jython 2.7.2.b3 https://bugs.jython.org/issue2826 opened by wfouche2 #2828: Upgrade netty from 4.1.24 https://bugs.jython.org/issue2828 opened by jeff.allen Most recent 15 issues with no replies (15) ========================================== #2828: Upgrade netty from 4.1.24 https://bugs.jython.org/issue2828 #2826: Unicode hex string decode fails with Jython 2.7.2.b3 https://bugs.jython.org/issue2826 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2792: Failures in test_import_jy from Java 13 https://bugs.jython.org/issue2792 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 #2770: PBKDF-OpenSSL SecretKeyFactory not available on Java 7 https://bugs.jython.org/issue2770 #2760: How to call procedure with use zxjdbc and get back OUT paramet https://bugs.jython.org/issue2760 #2754: Failure in Py.initProxy for class not at module level https://bugs.jython.org/issue2754 #2752: Allow Python functions to be used as a java.lang.FunctionalInt https://bugs.jython.org/issue2752 #2750: Make PyFunction implement java.util.concurrent.Callable<PyObje https://bugs.jython.org/issue2750 #2734: Re-work package scanning and cache for modules https://bugs.jython.org/issue2734 #2723: Unusual behavior in SimpleCookie when '=' and '@' is used in https://bugs.jython.org/issue2723 #2722: run-time issue while trying to reach external endpoint (Weathe https://bugs.jython.org/issue2722 #2720: wrap_scoket_exception: 'module' object has no attribute 'OP_NO https://bugs.jython.org/issue2720 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2230: Jython evaluation blocks under heavy load with high multi-core https://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 #1612: array.array should use specialized bulk operations to initiali https://bugs.jython.org/issue1612 #1435: traceback doesn't include Java stack trace in user functions https://bugs.jython.org/issue1435 Top 10 most discussed issues (1) ================================ #2820: Importing non-existing module fails with UnicodeDecodeError if https://bugs.jython.org/issue2820 5 msgs Issues closed (2) ================= #2804: Missing class com/google/common/base/CharMatcher https://bugs.jython.org/issue2804 closed by jeff.allen #2814: maven/build.xml does not PGP-sign the publication https://bugs.jython.org/issue2814 closed by jeff.allen |
|
From: Jim B. <jim...@py...> - 2019-11-04 12:20:53
|
I have briefly tried the 2.7.2b2 and it looks great. We should hopefully soon have much more extensive testing. Thanks so much for your work on this release! On Mon, Nov 4, 2019 at 2:10 AM fwi...@gm... <fwi...@gm...> wrote: > On Fri, Nov 1, 2019 at 2:02 PM Jeff Allen <ja...@fa...> wrote: > > > > We're there ... Jython 2.7.2b2 is at long last live. (There never was a > public 2.7.2b1.) Find it here: > Awesome! > > > Frank: > > > > could you do the bits only you know how, please? On the bug-tracker can > you make it possible to raise bugs against 2.7.1 and 2.7.2, and to have > milestones 2.7.3 and 2.7.4 ? > Bug tracker is updated with the new versions and milestones. It looks > like I don't have permission to remove versions or milestones, but let > me know if you want me to adjust the order. > > I'll put together an announcement shortly. > > -Frank > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: <fwi...@gm...> - 2019-11-04 01:09:56
|
On Fri, Nov 1, 2019 at 2:02 PM Jeff Allen <ja...@fa...> wrote: > > We're there ... Jython 2.7.2b2 is at long last live. (There never was a public 2.7.2b1.) Find it here: Awesome! > Frank: > > could you do the bits only you know how, please? On the bug-tracker can you make it possible to raise bugs against 2.7.1 and 2.7.2, and to have milestones 2.7.3 and 2.7.4 ? Bug tracker is updated with the new versions and milestones. It looks like I don't have permission to remove versions or milestones, but let me know if you want me to adjust the order. I'll put together an announcement shortly. -Frank |
|
From: Jeff A. <ja...@fa...> - 2019-11-01 21:02:29
|
We're there ... Jython 2.7.2b2 is at long last live. (There never was a public 2.7.2b1.) Find it here: jython-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython/2.7.2b2/) jython-installer-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython-installer/2.7.2b2/) jython-slim-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython-slim/2.7.2b2/) jython-standalone-2.7.2b2.jar (https://repo1.maven.org/maven2/org/python/jython-standalone/2.7.2b2/) As I write, these are not yet showing on https://search.maven.org/search?q=g:org.python but I assume it will catch up eventually. Maven and Gradle builds on my local machine already download jython-slim named as a dependency. Heartfelt thanks go to all who've contributed to this release. Now let's find out what the users make of it. Jeff Frank: could you do the bits only you know how, please? On the bug-tracker can you make it possible to raise bugs against 2.7.1 and 2.7.2, and to have milestones 2.7.3 and 2.7.4 ? Jeff -- Jeff Allen |
|
From: Jython t. <st...@bu...> - 2019-11-01 18:05:36
|
ACTIVITY SUMMARY (2019-10-25 - 2019-11-01) Jython tracker at https://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 345 ( +1) closed 2445 ( +0) total 2790 ( +1) Open issues with patches: 25 Issues opened (1) ================= #2818: Support for Redis Module in PythonInterpreter https://bugs.jython.org/issue2818 opened by rkanumola Most recent 15 issues with no replies (15) ========================================== #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2792: Failures in test_import_jy from Java 13 https://bugs.jython.org/issue2792 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 #2770: PBKDF-OpenSSL SecretKeyFactory not available on Java 7 https://bugs.jython.org/issue2770 #2760: How to call procedure with use zxjdbc and get back OUT paramet https://bugs.jython.org/issue2760 #2754: Failure in Py.initProxy for class not at module level https://bugs.jython.org/issue2754 #2752: Allow Python functions to be used as a java.lang.FunctionalInt https://bugs.jython.org/issue2752 #2750: Make PyFunction implement java.util.concurrent.Callable<PyObje https://bugs.jython.org/issue2750 #2736: ensurepip fails with: pip 9.0.1 requires SSL/TLS https://bugs.jython.org/issue2736 #2734: Re-work package scanning and cache for modules https://bugs.jython.org/issue2734 #2723: Unusual behavior in SimpleCookie when '=' and '@' is used in https://bugs.jython.org/issue2723 #2722: run-time issue while trying to reach external endpoint (Weathe https://bugs.jython.org/issue2722 #2720: wrap_scoket_exception: 'module' object has no attribute 'OP_NO https://bugs.jython.org/issue2720 #2713: Rounding a float field causes test_cpickle to fail https://bugs.jython.org/issue2713 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2330: full-build fails to copy CPython License https://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core https://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries https://bugs.jython.org/issue2121 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 Top 10 most discussed issues (1) ================================ #2816: Python Interpreter which uses Python and Redis script gives an https://bugs.jython.org/issue2816 3 msgs |
|
From: Jeff A. <ja...@fa...> - 2019-10-30 21:07:33
|
Ok, I think I have succeeded in getting acceptable bundles for the -slim and -installer versions to stage, although not by a reproducible process. https://oss.sonatype.org/content/repositories/orgpython-1079/org/python/jython-installer/2.7.2b1/ https://oss.sonatype.org/content/repositories/orgpython-1078/org/python/jython-slim/2.7.2b1/ If I've understood correctly, this is one button-push away from publishing an actual release. However, I'll go through it all cleanly (that is, committed, tagged and using scripts) and call the result 2.7.2b2. Jeff Allen On 26/10/2019 13:55, Jeff Allen wrote: > > Hi Frank: > > I have some time now to try again, and the access to run the whole > process for myself (thanks). I'll dry run quietly with 2.7.2b1 and aim > for an official b2, enlisting your help to make it known. > > I fixed the gpg thing (see https://bugs.jython.org/issue2814) although > I quite like the look of > https://central.sonatype.org/pages/apache-ant.html#signing-and-deployments-using-the-maven-ant-tasks > as an alternative to exec-ing gpg. I think the requirements have > tightened since the previous release so signing will not be the only > blocker. > > I'm sure I can figure it out, but did you learn anything in your > staging attempts that I can get the easy way? > > Jeff > > Jeff Allen > On 13/10/2019 09:06, Jeff Allen wrote: >> On 13/10/2019 05:40, fwi...@gm... wrote: >>> On Sat, Oct 12, 2019 at 2:19 PM Jeff Allen<ja...@fa...> wrote: >>>> Hi Frank: >>>> >>>> Evidently this is keeping you up late. If it hasn't suddenly come right for you, I think I should take this back: seems we're not ready. >>> No worries! Since I'm the only one that has released Jython in the >>> last decade or so, I'm sure there is something peculiar in my >>> environment that is interacting poorly with the current changes. I bet >>> if I grab an old version of build.xml I may be able to get the process >>> to work. I don't have time tonight but I'm sure I can give it a try >>> tomorrow. >> >> Ok, well let us know when you've had enough :). Meanwhile I'll learn >> what I can about the process. The video >> <https://youtu.be/dXR4pJ_zS-0?t=300> suggests that when it fails >> there's quite a lot of evidence where the bundle contents are defective. >> >> An old ./maven/build.xml is worth trying. I'm confident the current >> main ./build.xml delivers the right things. The safeguards are all in >> the main one (that stop you labeling what you build as a release if >> it didn't come from a clean and tagged state). >> >>>> I've got myself GnuPG. I think I could dry run the whole process, fixing my broken scripts as I go, as I did with the rest.I think the outcome would now have to be tagged v2.7.2b2 to avoid confusion. A parallel possibility is to post v2.7.2b1 somewhere and just link it from the website. >>>> >>> A v2.2.2b2 sounds perfectly fine to me if it turns out that I'm unable >>> to get the current version working, but I do want to give it another >>> try. Once I figure out what is needed I'll make sure to let everyone >>> know what the fix was. >> Yes please! We have to encapsulate all this magic in the scripts or >> the instructions. >>> -Frank >> Jeff > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
|
From: Jeff A. <ja...@fa...> - 2019-10-26 12:56:07
|
Hi Frank: I have some time now to try again, and the access to run the whole process for myself (thanks). I'll dry run quietly with 2.7.2b1 and aim for an official b2, enlisting your help to make it known. I fixed the gpg thing (see https://bugs.jython.org/issue2814) although I quite like the look of https://central.sonatype.org/pages/apache-ant.html#signing-and-deployments-using-the-maven-ant-tasks as an alternative to exec-ing gpg. I think the requirements have tightened since the previous release so signing will not be the only blocker. I'm sure I can figure it out, but did you learn anything in your staging attempts that I can get the easy way? Jeff Jeff Allen On 13/10/2019 09:06, Jeff Allen wrote: > On 13/10/2019 05:40, fwi...@gm... wrote: >> On Sat, Oct 12, 2019 at 2:19 PM Jeff Allen<ja...@fa...> wrote: >>> Hi Frank: >>> >>> Evidently this is keeping you up late. If it hasn't suddenly come right for you, I think I should take this back: seems we're not ready. >> No worries! Since I'm the only one that has released Jython in the >> last decade or so, I'm sure there is something peculiar in my >> environment that is interacting poorly with the current changes. I bet >> if I grab an old version of build.xml I may be able to get the process >> to work. I don't have time tonight but I'm sure I can give it a try >> tomorrow. > > Ok, well let us know when you've had enough :). Meanwhile I'll learn > what I can about the process. The video > <https://youtu.be/dXR4pJ_zS-0?t=300> suggests that when it fails > there's quite a lot of evidence where the bundle contents are defective. > > An old ./maven/build.xml is worth trying. I'm confident the current > main ./build.xml delivers the right things. The safeguards are all in > the main one (that stop you labeling what you build as a release if it > didn't come from a clean and tagged state). > >>> I've got myself GnuPG. I think I could dry run the whole process, fixing my broken scripts as I go, as I did with the rest.I think the outcome would now have to be tagged v2.7.2b2 to avoid confusion. A parallel possibility is to post v2.7.2b1 somewhere and just link it from the website. >>> >> A v2.2.2b2 sounds perfectly fine to me if it turns out that I'm unable >> to get the current version working, but I do want to give it another >> try. Once I figure out what is needed I'll make sure to let everyone >> know what the fix was. > Yes please! We have to encapsulate all this magic in the scripts or > the instructions. >> -Frank > Jeff |
|
From: Adam B. <ada...@gm...> - 2019-10-26 08:49:39
|
Hi Ravneet Firstly, did you realise the latest official release is 2.7.1? 2.7.2 beta should also be soon. 2.5.3 is quite old. 2.7.1 and 2.7.2 include a number of specifically security fixes, since that seems to be the main driver for yourselves. I imagine at least some of the fixes you've been applying have already been applied to the current dev version. If you have made patches that haven't otherwise been picked up, it would be great if you could contribute them back, going through the usual review process, of course. That would also mean minimal merge effort to you when they were in the trunk. On end of life. The informal consensus is that as there isn't a Jython 3.x yet, it would be unreasonable to make Jython 2.x EOL at the same date as CPython 2.x, and Jython 2.x will continue well into 2020. The core Jython devs and the PSF are trying to get a clearer statement on dates together that both can be fairly happy with. Cheers Adam On Fri, 25 Oct 2019 at 23:55, Ravneet Singh <rav...@al...> wrote: > Hi Team > > > > We are using Jython 2.5.3, and those Jython libraries contains Python > files also. Now for any security vulnerability reported in Python 2.X , we > had been referring the solution from python.org website and updating > those code files in the Jython libraries. Now since Python 2.X is going End > Of Life as mentioned by python.org from Jan 2020, then we have few > questions here: > > 1. How can we get the security fixes for the security issues/CVEs > reported in python 2.X files which are also used in Jython library. > 2. And, will jython.org would be providing the security fixes for the > security issues/CVEs reported in Python 2.X . > 3. And, when will the Jython 3 corresponding to Python 3.X getting > released. Is there any proposed date for the same. > > > > Apart from this, any suggestion from your side for users of Jython 2.X > taking in view that Python 2 is going End of Life. > > > > Thanks > > Ravneet Singh > ===================================================== > Please refer to https://northamerica.altran.com/email-disclaimer > for important disclosures regarding this electronic communication. > ===================================================== > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Jython t. <st...@bu...> - 2019-10-25 18:05:34
|
ACTIVITY SUMMARY (2019-10-18 - 2019-10-25) Jython tracker at https://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 344 ( +1) closed 2445 ( +0) total 2789 ( +1) Open issues with patches: 25 Issues opened (1) ================= #2816: Python Interpreter which uses Python and Redis script gives an https://bugs.jython.org/issue2816 opened by rkanumola Most recent 15 issues with no replies (15) ========================================== #2816: Python Interpreter which uses Python and Redis script gives an https://bugs.jython.org/issue2816 #2802: PEP 0263 magic coding comment rejected in UTF-8 https://bugs.jython.org/issue2802 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2792: Failures in test_import_jy from Java 13 https://bugs.jython.org/issue2792 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 #2770: PBKDF-OpenSSL SecretKeyFactory not available on Java 7 https://bugs.jython.org/issue2770 #2760: How to call procedure with use zxjdbc and get back OUT paramet https://bugs.jython.org/issue2760 #2754: Failure in Py.initProxy for class not at module level https://bugs.jython.org/issue2754 #2752: Allow Python functions to be used as a java.lang.FunctionalInt https://bugs.jython.org/issue2752 #2750: Make PyFunction implement java.util.concurrent.Callable<PyObje https://bugs.jython.org/issue2750 #2736: ensurepip fails with: pip 9.0.1 requires SSL/TLS https://bugs.jython.org/issue2736 #2734: Re-work package scanning and cache for modules https://bugs.jython.org/issue2734 #2723: Unusual behavior in SimpleCookie when '=' and '@' is used in https://bugs.jython.org/issue2723 #2722: run-time issue while trying to reach external endpoint (Weathe https://bugs.jython.org/issue2722 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2330: full-build fails to copy CPython License https://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core https://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries https://bugs.jython.org/issue2121 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 |
|
From: Ravneet S. <rav...@al...> - 2019-10-25 13:54:27
|
Hi Team We are using Jython 2.5.3, and those Jython libraries contains Python files also. Now for any security vulnerability reported in Python 2.X , we had been referring the solution from python.org website and updating those code files in the Jython libraries. Now since Python 2.X is going End Of Life as mentioned by python.org from Jan 2020, then we have few questions here: 1. How can we get the security fixes for the security issues/CVEs reported in python 2.X files which are also used in Jython library. 2. And, will jython.org would be providing the security fixes for the security issues/CVEs reported in Python 2.X . 3. And, when will the Jython 3 corresponding to Python 3.X getting released. Is there any proposed date for the same. Apart from this, any suggestion from your side for users of Jython 2.X taking in view that Python 2 is going End of Life. Thanks Ravneet Singh ===================================================== Please refer to https://northamerica.altran.com/email-disclaimer for important disclosures regarding this electronic communication. ===================================================== |
|
From: Rory O'D. <ror...@or...> - 2019-10-20 06:52:06
|
Hi Alan, *OpenJDK builds - JDK 14 *- Early Access build 19 is available at http://jdk.java.net/14/ These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release notes o https://jdk.java.net/14/release-notes * JEPs targeted to JDK 14, so far o 352 - Non-Volatile Mapped Byte Buffers <https://openjdk.java.net/jeps/352> o 358 - Helpful NullPointerExceptions <http://openjdk.java.net/jeps/358> o 349 - JFR Event Streaming <https://openjdk.java.net/jeps/349> * *I want to draw your attention to some notable changes in previous builds of JDK 14.* o *Build 14* - Classes are now loaded and linked by Class.forName() (JDK-8212117 <https://bugs.openjdk.java.net/browse/JDK-8212117>) + we need help testing changes to 3-arg Class.forName method. The method has always been specified to link the class but the implementation has historically not done this when invoked with the "initialize" parameter set to false. The bug has been fixed in JDK 14 but it has the potential to change the behavior of code that uses Class.forName to load classes that cannot be linked. * Changes in this build <https://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-14%2B18%22%3A%3A%22jdk-14%2B19%22-%22jdk-14%2B18%22%29&revcount=1000> *Openjdk Builds - JDK 13.0.1 *General Availability - https://jdk.java.net/13/ These early-access, open-source builds are provided under the GNU General Public License, version 2, with the Classpath Exception <http://openjdk.java.net/legal/gplv2+ce.html>. * Release notes <https://jdk.java.net/13/release-notes> * Changes in this release <https://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13.0.1%2B8%22%3A%3A%22jdk-13.0.1%2B9%22-%22jdk-13.0.1%2B8%22%29&revcount=1000> *Crypto roadmap updated* - https://www.java.com/en/jre-jdk-cryptoroadmap.html Targeted Date^(2) Targeted Release(s) Algorithm/Protocol Action How to test/enable change Change Log 2019-10-15 13, 11, 8, 7 ECC on TLS Disable non-NIST Suite B EC curves (sect283k1, sect283r1, sect409k1, sect409r1, sect571k1, sect571r1, secp256k1) when negotiating TLS sessions Disabling non-NIST Suite B EC curves when negotiating TLS sessions <https://java.com/en/configure_crypto.html#DisablenonNIST> 2019-10-08 Announced. Rgds,Rory -- Rgds, Rory O'Donnell Quality Engineering Manager Oracle EMEA, Dublin, Ireland |
|
From: Jython t. <st...@bu...> - 2019-10-18 18:05:39
|
ACTIVITY SUMMARY (2019-10-11 - 2019-10-18) Jython tracker at https://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 343 ( +0) closed 2445 ( +0) total 2788 ( +0) Open issues with patches: 25 Most recent 15 issues with no replies (15) ========================================== #2802: PEP 0263 magic coding comment rejected in UTF-8 https://bugs.jython.org/issue2802 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2792: Failures in test_import_jy from Java 13 https://bugs.jython.org/issue2792 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 #2770: PBKDF-OpenSSL SecretKeyFactory not available on Java 7 https://bugs.jython.org/issue2770 #2760: How to call procedure with use zxjdbc and get back OUT paramet https://bugs.jython.org/issue2760 #2754: Failure in Py.initProxy for class not at module level https://bugs.jython.org/issue2754 #2752: Allow Python functions to be used as a java.lang.FunctionalInt https://bugs.jython.org/issue2752 #2750: Make PyFunction implement java.util.concurrent.Callable<PyObje https://bugs.jython.org/issue2750 #2736: ensurepip fails with: pip 9.0.1 requires SSL/TLS https://bugs.jython.org/issue2736 #2734: Re-work package scanning and cache for modules https://bugs.jython.org/issue2734 #2723: Unusual behavior in SimpleCookie when '=' and '@' is used in https://bugs.jython.org/issue2723 #2722: run-time issue while trying to reach external endpoint (Weathe https://bugs.jython.org/issue2722 #2720: wrap_scoket_exception: 'module' object has no attribute 'OP_NO https://bugs.jython.org/issue2720 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2330: full-build fails to copy CPython License https://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core https://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries https://bugs.jython.org/issue2121 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 |
|
From: Jeff A. <ja...@fa...> - 2019-10-13 08:20:33
|
On 13/10/2019 05:40, fwi...@gm... wrote: > On Sat, Oct 12, 2019 at 2:19 PM Jeff Allen <ja...@fa...> wrote: >> Hi Frank: >> >> Evidently this is keeping you up late. If it hasn't suddenly come right for you, I think I should take this back: seems we're not ready. > No worries! Since I'm the only one that has released Jython in the > last decade or so, I'm sure there is something peculiar in my > environment that is interacting poorly with the current changes. I bet > if I grab an old version of build.xml I may be able to get the process > to work. I don't have time tonight but I'm sure I can give it a try > tomorrow. Ok, well let us know when you've had enough :). Meanwhile I'll learn what I can about the process. The video <https://youtu.be/dXR4pJ_zS-0?t=300> suggests that when it fails there's quite a lot of evidence where the bundle contents are defective. An old ./maven/build.xml is worth trying. I'm confident the current main ./build.xml delivers the right things. The safeguards are all in the main one (that stop you labeling what you build as a release if it didn't come from a clean and tagged state). >> I've got myself GnuPG. I think I could dry run the whole process, fixing my broken scripts as I go, as I did with the rest.I think the outcome would now have to be tagged v2.7.2b2 to avoid confusion. A parallel possibility is to post v2.7.2b1 somewhere and just link it from the website. >> > A v2.2.2b2 sounds perfectly fine to me if it turns out that I'm unable > to get the current version working, but I do want to give it another > try. Once I figure out what is needed I'll make sure to let everyone > know what the fix was. Yes please! We have to encapsulate all this magic in the scripts or the instructions. > -Frank Jeff |
|
From: <fwi...@gm...> - 2019-10-13 04:40:54
|
On Sat, Oct 12, 2019 at 2:19 PM Jeff Allen <ja...@fa...> wrote: > > Hi Frank: > > Evidently this is keeping you up late. If it hasn't suddenly come right for you, I think I should take this back: seems we're not ready. No worries! Since I'm the only one that has released Jython in the last decade or so, I'm sure there is something peculiar in my environment that is interacting poorly with the current changes. I bet if I grab an old version of build.xml I may be able to get the process to work. I don't have time tonight but I'm sure I can give it a try tomorrow. > I've got myself GnuPG. I think I could dry run the whole process, fixing my broken scripts as I go, as I did with the rest.I think the outcome would now have to be tagged v2.7.2b2 to avoid confusion. A parallel possibility is to post v2.7.2b1 somewhere and just link it from the website. > A v2.2.2b2 sounds perfectly fine to me if it turns out that I'm unable to get the current version working, but I do want to give it another try. Once I figure out what is needed I'll make sure to let everyone know what the fix was. -Frank |
|
From: Jeff A. <ja...@fa...> - 2019-10-12 21:19:30
|
Hi Frank: Evidently this is keeping you up late. If it hasn't suddenly come right for you, I think I should take this back: seems we're not ready. I've got myself GnuPG. I think I could dry run the whole process, fixing my broken scripts as I go, as I did with the rest.I think the outcome would now have to be tagged v2.7.2b2 to avoid confusion. A parallel possibility is to post v2.7.2b1 somewhere and just link it from the website. Jeff On 11/10/2019 07:03, fwi...@gm... wrote: > I have the bundles built and gpg signed, but I'm still missing > something that prevents me from finalizing the uploads, I'll keep > trying and post here when we have soft releases available. > >> You have various channels under your control: I don't see why you wouldn't use those with much the same announcement as before. I'm able to update the website. (I think we want to show 2.7.1 as current and the beta alongside.) It's adveretising. Let's do everything. >> > Sounds good, when I get the release uploaded I will do the > announcements as usual. > >> All: Any thoughts on target duration? I think maybe a fixed 6 weeks (subject to personal commitments) and the next thing is either b2 or rc1 depending on how many new bugs appear and their criticality. > 6 weeks works for me. > > -Frank > |
|
From: Jython t. <st...@bu...> - 2019-10-11 18:05:35
|
ACTIVITY SUMMARY (2019-10-04 - 2019-10-11) Jython tracker at https://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 343 ( +2) closed 2445 ( +0) total 2788 ( +2) Open issues with patches: 25 Issues opened (2) ================= #2812: Failure in test_sort.TestBase.testStressfully on Java 11 https://bugs.jython.org/issue2812 opened by jeff.allen #2814: maven/build.xml does not PGP-sign the publication https://bugs.jython.org/issue2814 opened by jeff.allen Most recent 15 issues with no replies (15) ========================================== #2802: PEP 0263 magic coding comment rejected in UTF-8 https://bugs.jython.org/issue2802 #2798: OpenJDK 1.7.0_75-b13 string regrtest OutOfMemory on windows https://bugs.jython.org/issue2798 #2794: invocation_tests.py missing from modjy tests https://bugs.jython.org/issue2794 #2792: Failures in test_import_jy from Java 13 https://bugs.jython.org/issue2792 #2790: Equivalent signal handlers do not test equal using == https://bugs.jython.org/issue2790 #2770: PBKDF-OpenSSL SecretKeyFactory not available on Java 7 https://bugs.jython.org/issue2770 #2760: How to call procedure with use zxjdbc and get back OUT paramet https://bugs.jython.org/issue2760 #2754: Failure in Py.initProxy for class not at module level https://bugs.jython.org/issue2754 #2752: Allow Python functions to be used as a java.lang.FunctionalInt https://bugs.jython.org/issue2752 #2750: Make PyFunction implement java.util.concurrent.Callable<PyObje https://bugs.jython.org/issue2750 #2736: ensurepip fails with: pip 9.0.1 requires SSL/TLS https://bugs.jython.org/issue2736 #2734: Re-work package scanning and cache for modules https://bugs.jython.org/issue2734 #2723: Unusual behavior in SimpleCookie when '=' and '@' is used in https://bugs.jython.org/issue2723 #2722: run-time issue while trying to reach external endpoint (Weathe https://bugs.jython.org/issue2722 #2720: wrap_scoket_exception: 'module' object has no attribute 'OP_NO https://bugs.jython.org/issue2720 Most recent 15 issues waiting for review (15) ============================================= #2566: inspect does not recognize code objects from bytecode files https://bugs.jython.org/issue2566 #2545: help() does not work on Java-implemented modules https://bugs.jython.org/issue2545 #2429: cStringIO does not work with mutable objects implementing the https://bugs.jython.org/issue2429 #2367: Jython ignores custom __eq__ when hashing dict subclasses https://bugs.jython.org/issue2367 #2363: relative seeks works incorrectly after readline https://bugs.jython.org/issue2363 #2330: full-build fails to copy CPython License https://bugs.jython.org/issue2330 #2230: Jython evaluation blocks under heavy load with high multi-core https://bugs.jython.org/issue2230 #2143: site-packages support in standalone jar https://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context https://bugs.jython.org/issue2142 #2121: Jython jar on Maven central embeds other third party libraries https://bugs.jython.org/issue2121 #1925: Support loading java.sql.Drivers that aren't on the boot class https://bugs.jython.org/issue1925 #1917: No ctypes.c_char https://bugs.jython.org/issue1917 #1842: Add IBM i support to Jython https://bugs.jython.org/issue1842 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo https://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject https://bugs.jython.org/issue1646 Top 10 most discussed issues (1) ================================ #2810: NoSuchMethodError in test_jython_initializer Java 10+ https://bugs.jython.org/issue2810 6 msgs |
|
From: Adam B. <ada...@gm...> - 2019-10-11 07:17:05
|
+1 on a six week beta Adam > 在 2019年10月11日，下午5:01，Jeff Allen <ja...@fa...> 写道： > > On 11/10/2019 07:03, fwi...@gm... wrote: >> I have the bundles built and gpg signed, but I'm still missing >> something that prevents me from finalizing the uploads, I'll keep >> trying and post here when we have soft releases available. > It's disappointing the upload tool (website I assume) doesn't pinpoint the problem. I think I'd misunderstood earlier: we sign JARs and POM individually and bundle don't we, rather than sign each bundle? So where my build stops (with 4 purported bundles) isn't a feasible starting point: the problem is further back, and these "bundles" don't have signatures for the objects inside. So (explaining to myself), it's the contents of ./build/maven that need (individually) signing, as generated by the targets bundle, bundle-standalone, etc.. > > The maven/build.xml we inherited is this: https://hg.python.org/jython/file/3b424500eab9/maven/build.xml and my changes have been to eliminate the hard-coding of project.version and to include the Gradle-built JAR if it exists. I also changed build.dir to build.maven (=./build/maven), because the same name meaning something completely different from in the main build was confusing me. > > I thought it odd that the hard-coding was for 2.7.0 beta, whereas I know we have published several times since then. This suggests we didn't inherit the latest version. > > If this gets too tangled, we could suspend the attempt and I'll try to develop (and encapsulate) a working publication process, tested against an account I create and own. But Sonatype confuses me: I haven't even found the place it invites me to make such an account. > > Jeff > >>> You have various channels under your control: I don't see why you wouldn't use those with much the same announcement as before. I'm able to update the website. (I think we want to show 2.7.1 as current and the beta alongside.) It's adveretising. Let's do everything. >>> >> Sounds good, when I get the release uploaded I will do the >> announcements as usual. >> >>> All: Any thoughts on target duration? I think maybe a fixed 6 weeks (subject to personal commitments) and the next thing is either b2 or rc1 depending on how many new bugs appear and their criticality. >> 6 weeks works for me. >> >> -Frank >> > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
|
From: Jeff A. <ja...@fa...> - 2019-10-11 07:00:44
|
On 11/10/2019 07:03, fwi...@gm... wrote: > I have the bundles built and gpg signed, but I'm still missing > something that prevents me from finalizing the uploads, I'll keep > trying and post here when we have soft releases available. It's disappointing the upload tool (website I assume) doesn't pinpoint the problem. I think I'd misunderstood earlier: we sign JARs and POM individually and bundle don't we, rather than sign each bundle? So where my build stops (with 4 purported bundles) isn't a feasible starting point: the problem is further back, and these "bundles" don't have signatures for the objects inside. So (explaining to myself), it's the contents of ./build/maven that need (individually) signing, as generated by the targets bundle, bundle-standalone, etc.. The maven/build.xml we inherited is this: https://hg.python.org/jython/file/3b424500eab9/maven/build.xml and my changes have been to eliminate the hard-coding of project.version and to include the Gradle-built JAR if it exists. I also changed build.dir to build.maven (=./build/maven), because the same name meaning something completely different from in the main build was confusing me. I thought it odd that the hard-coding was for 2.7.0 beta, whereas I know we have published several times since then. This suggests we didn't inherit the latest version. If this gets too tangled, we could suspend the attempt and I'll try to develop (and encapsulate) a working publication process, tested against an account I create and own. But Sonatype confuses me: I haven't even found the place it invites me to make such an account. Jeff >> You have various channels under your control: I don't see why you wouldn't use those with much the same announcement as before. I'm able to update the website. (I think we want to show 2.7.1 as current and the beta alongside.) It's adveretising. Let's do everything. >> > Sounds good, when I get the release uploaded I will do the > announcements as usual. > >> All: Any thoughts on target duration? I think maybe a fixed 6 weeks (subject to personal commitments) and the next thing is either b2 or rc1 depending on how many new bugs appear and their criticality. > 6 weeks works for me. > > -Frank > |
|
From: <fwi...@gm...> - 2019-10-11 06:04:37
|
I have the bundles built and gpg signed, but I'm still missing something that prevents me from finalizing the uploads, I'll keep trying and post here when we have soft releases available. > You have various channels under your control: I don't see why you wouldn't use those with much the same announcement as before. I'm able to update the website. (I think we want to show 2.7.1 as current and the beta alongside.) It's adveretising. Let's do everything. > Sounds good, when I get the release uploaded I will do the announcements as usual. > All: Any thoughts on target duration? I think maybe a fixed 6 weeks (subject to personal commitments) and the next thing is either b2 or rc1 depending on how many new bugs appear and their criticality. 6 weeks works for me. -Frank |
|
From: Jeff A. <ja...@fa...> - 2019-10-10 08:47:37
|
On 10/10/2019 06:26, fwi...@gm... wrote: > OK - I got my environment issues worked out (some dumb stuff with my > local brew setup and mercurial), and I was able to follow the release > procedure here: > https://jython-devguide.readthedocs.io/en/latest/release_jy.html I > think the release process and docs are in good shape. I avoided > looking at the gradle stuff for now :) Thanks for diving in. If I understand correctly, you don't need to install Gradle because .\gradlew (w is for wrapper, not Windows) and its subdirectory brings all you need. > In section 23.1.7, it suggests that that I run `ant full-check` and > later suggests that this will create a build, but I think we want `ant > full-build`, does that sound right? I'm rusty so I could be missing > something. In 23.1.7 we run full-check again as a safety check that we're actually at the tag, that the output prints what you see in the display box. The build does various integrity checks. In the subsequent paragraph (text), it says to run the full-build. Could be more explicit. > On OSX I get one extra failure on `test_socket_jy` but it looks > similar to the test_ssl_jy failure so not a big deal IMO. I find networking tests have to be taken with a pinch of salt on personal devices, I think because of their interaction with security products or ISA DNS hijacking. OTOH networking is an area where Jython hangs by a thread (or many concurrent threads :). I take some comfort that this ran ok on CI: https://travis-ci.org/jythontools/jython/jobs/595290735#L647 > I think it looks like a step was removed from maven/build.xml - it > previously gpg signed the bundles to be uploaded to maven. I think > this step is necessary to publish the bundles. I'll look into it in > more detail tomorrow. Yes, it failed gracelessly on my machine and looked optional (https://hg.python.org/jython/file/05f61ba4d447/maven/build.xml#l172). Presumably the person using the script has to have a (your) private key anyway for the result to be acceptable. It looks like the signatures will sit alongside the JAR files as separate files, but I don't know the tool. Sorry, I should have created a personal account at Sonatype to dry-run this. Could it be done manually at the prompt for now? Note that the location of the bundles is ./publications now and that's all there is in it, so easy to glob. If you edit maven/build.xml the safeguards will force you to make a snapshot becuase you have changes not checked-in at the tag. I have raised issue 2814 to fix. > But, progress - almost there! > > BTW when I get this all published, would you want to do the > announcement Jeff? I'm happy to do it, but I'm also happy to just > point to your announcement if you would like to do it. You have various channels under your control: I don't see why you wouldn't use those with much the same announcement as before. I'm able to update the website. (I think we want to show 2.7.1 as current and the beta alongside.) It's adveretising. Let's do everything. All: Any thoughts on target duration? I think maybe a fixed 6 weeks (subject to personal commitments) and the next thing is either b2 or rc1 depending on how many new bugs appear and their criticality. Jeff |
|
From: <fwi...@gm...> - 2019-10-10 05:26:48
|
OK - I got my environment issues worked out (some dumb stuff with my local brew setup and mercurial), and I was able to follow the release procedure here: https://jython-devguide.readthedocs.io/en/latest/release_jy.html I think the release process and docs are in good shape. I avoided looking at the gradle stuff for now :) In section 23.1.7, it suggests that that I run `ant full-check` and later suggests that this will create a build, but I think we want `ant full-build`, does that sound right? I'm rusty so I could be missing something. On OSX I get one extra failure on `test_socket_jy` but it looks similar to the test_ssl_jy failure so not a big deal IMO. I think it looks like a step was removed from maven/build.xml - it previously gpg signed the bundles to be uploaded to maven. I think this step is necessary to publish the bundles. I'll look into it in more detail tomorrow. But, progress - almost there! BTW when I get this all published, would you want to do the announcement Jeff? I'm happy to do it, but I'm also happy to just point to your announcement if you would like to do it. -Frank |
|
From: <fwi...@gm...> - 2019-10-09 05:42:54
|
On Tue, Oct 8, 2019 at 12:58 PM Jeff Allen <ja...@fa...> wrote: > > Ok, let's do it! Great! I have started giving it a try locally but have run into a few problems. I'm pretty sure all of the problems are on me - I will reach out if I think I need help. I'll keep trying tonight but I think getting my cobwebs out of my environment is probably going to take more than one day. I will keep you posted. -Frank |
101 messages has been excluded from this view by a project administrator.
