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
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Darjus L. <da...@gm...> - 2016-02-03 05:31:00
|
Looks good for me on Mac On Wed, Feb 3, 2016 at 3:22 PM fwi...@gm... <fwi...@gm...> wrote: > Hi all, > > Doing the soft launch thing for 2.7.1 beta3. > Please test, especially if you can test on windows! > > The releases: > > installer: > https://oss.sonatype.org/content/repositories/orgpython-1060/org/python/jython-installer/2.7.1b3/jython-installer-2.7.1b3.jar > > standalone: > https://oss.sonatype.org/content/repositories/orgpython-1061/org/python/jython-standalone/2.7.1b3/jython-standalone-2.7.1b3.jar > > The parent directories of each of the above have the checksums, source > jars, javadocs, etc. > > -Frank > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: <fwi...@gm...> - 2016-02-03 04:21:45
|
Hi all, Doing the soft launch thing for 2.7.1 beta3. Please test, especially if you can test on windows! The releases: installer: https://oss.sonatype.org/content/repositories/orgpython-1060/org/python/jython-installer/2.7.1b3/jython-installer-2.7.1b3.jar standalone: https://oss.sonatype.org/content/repositories/orgpython-1061/org/python/jython-standalone/2.7.1b3/jython-standalone-2.7.1b3.jar The parent directories of each of the above have the checksums, source jars, javadocs, etc. -Frank |
From: Jython t. <st...@bu...> - 2016-01-29 17:10:21
|
ACTIVITY SUMMARY (2016-01-22 - 2016-01-29) 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 252 ( -2) closed 2222 ( +2) total 2474 ( +0) Open issues with patches: 27 Most recent 15 issues with no replies (15) ========================================== #2455: Java classes in packages with __init__.py not found http://bugs.jython.org/issue2455 #2447: Support server-side STARTTLS for SSL http://bugs.jython.org/issue2447 #2446: Support SNI for SSL/TLS http://bugs.jython.org/issue2446 #2443: java.util.Map derived classes lack iterkeys, itervalues method http://bugs.jython.org/issue2443 #2422: test_classpathimporter fauls on Linux http://bugs.jython.org/issue2422 #2418: test_chdir subprocess tests fail on Windows http://bugs.jython.org/issue2418 #2410: Regression in PySystemStateTest (leading slash) http://bugs.jython.org/issue2410 #2408: Redo sre port for regular expression support http://bugs.jython.org/issue2408 #2395: Parser bug with unparenthesized genexp with star-args http://bugs.jython.org/issue2395 #2369: running jython-standalone.jar in desktops with with korean lan http://bugs.jython.org/issue2369 #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 Most recent 15 issues waiting for review (15) ============================================= #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 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #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 #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 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1767: Rich comparisons http://bugs.jython.org/issue1767 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject http://bugs.jython.org/issue1646 |
From: Jython t. <st...@bu...> - 2016-01-22 17:10:22
|
ACTIVITY SUMMARY (2016-01-15 - 2016-01-22) 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 254 ( -7) closed 2220 ( +9) total 2474 ( +2) Open issues with patches: 27 Issues opened (2) ================= #2454: Security Vulnerability in Jython http://bugs.jython.org/issue2454 opened by cschneider4711 #2455: Java classes in packages with __init__.py not found http://bugs.jython.org/issue2455 opened by jsaiz Most recent 15 issues with no replies (15) ========================================== #2455: Java classes in packages with __init__.py not found http://bugs.jython.org/issue2455 #2447: Support server-side STARTTLS for SSL http://bugs.jython.org/issue2447 #2446: Support SNI for SSL/TLS http://bugs.jython.org/issue2446 #2443: java.util.Map derived classes lack iterkeys, itervalues method http://bugs.jython.org/issue2443 #2422: test_classpathimporter fauls on Linux http://bugs.jython.org/issue2422 #2418: test_chdir subprocess tests fail on Windows http://bugs.jython.org/issue2418 #2410: Regression in PySystemStateTest (leading slash) http://bugs.jython.org/issue2410 #2408: Redo sre port for regular expression support http://bugs.jython.org/issue2408 #2395: Parser bug with unparenthesized genexp with star-args http://bugs.jython.org/issue2395 #2369: running jython-standalone.jar in desktops with with korean lan http://bugs.jython.org/issue2369 #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 Most recent 15 issues waiting for review (15) ============================================= #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 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #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 #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 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1767: Rich comparisons http://bugs.jython.org/issue1767 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject http://bugs.jython.org/issue1646 Top 10 most discussed issues (2) ================================ #2441: sys.executable is None on standalone install, thus causing a s http://bugs.jython.org/issue2441 5 msgs #2454: Security Vulnerability in Jython http://bugs.jython.org/issue2454 5 msgs |
From: Jython t. <st...@bu...> - 2016-01-15 17:10:21
|
ACTIVITY SUMMARY (2016-01-08 - 2016-01-15) 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 261 (-12) closed 2211 (+14) total 2472 ( +2) Open issues with patches: 27 Issues opened (2) ================= #2401: SSL race produces NPE http://bugs.jython.org/issue2401 reopened by zyasoft #2453: org.python.modules.sre.PatternObject should be named SRE_Patte http://bugs.jython.org/issue2453 opened by darjus Most recent 15 issues with no replies (15) ========================================== #2447: Support server-side STARTTLS for SSL http://bugs.jython.org/issue2447 #2446: Support SNI for SSL/TLS http://bugs.jython.org/issue2446 #2443: java.util.Map derived classes lack iterkeys, itervalues method http://bugs.jython.org/issue2443 #2422: test_classpathimporter fauls on Linux http://bugs.jython.org/issue2422 #2418: test_chdir subprocess tests fail on Windows http://bugs.jython.org/issue2418 #2410: Regression in PySystemStateTest (leading slash) http://bugs.jython.org/issue2410 #2408: Redo sre port for regular expression support http://bugs.jython.org/issue2408 #2395: Parser bug with unparenthesized genexp with star-args http://bugs.jython.org/issue2395 #2369: running jython-standalone.jar in desktops with with korean lan http://bugs.jython.org/issue2369 #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 Most recent 15 issues waiting for review (15) ============================================= #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 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #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 #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 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1767: Rich comparisons http://bugs.jython.org/issue1767 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject http://bugs.jython.org/issue1646 Top 10 most discussed issues (4) ================================ #2401: SSL race produces NPE http://bugs.jython.org/issue2401 5 msgs #2360: Not installing pip on Jython http://bugs.jython.org/issue2360 4 msgs #2362: Import * doesn't work on JDK9 http://bugs.jython.org/issue2362 3 msgs #2445: Eclipse's DelegatingFeatureMap has MRO conflict http://bugs.jython.org/issue2445 3 msgs Issues closed (8) ================= #1712: jython.bat vs jython - difference in argument handling http://bugs.jython.org/issue1712 closed by zyasoft #1750: subst fails http://bugs.jython.org/issue1750 closed by zyasoft #1916: No ctypes.util http://bugs.jython.org/issue1916 closed by zyasoft #1958: Installer should not install two "jython" scripts http://bugs.jython.org/issue1958 closed by zyasoft #2177: Temporary files created on jython startup http://bugs.jython.org/issue2177 closed by zyasoft #2187: Windows doc needs to specify setting the classpath http://bugs.jython.org/issue2187 closed by zyasoft #2452: Jython locking threads on Java proxy objects (multithreaded pe http://bugs.jython.org/issue2452 closed by darjus #550200: Jython does not work on ebcdic platforms http://bugs.jython.org/issue550200 closed by zyasoft |
From: Darjus L. <da...@gm...> - 2016-01-13 23:40:33
|
Wow, really nice read regarding #2401 ! On Thu, Jan 14, 2016 at 10:21 AM Jim Baker <jim...@py...> wrote: > Agreed about almost being there! After further investigation, the zlib > fixes look straightforward; these fixes will also include support for the > gzip compression, which is tested as part of the urllib3 test suite. > > There was some recent activity on http://bugs.jython.org/issue2401 It was > interesting to be writing up commentary about this on the Netty Google > Group thread while Netty was simultaneously releasing a bug fix... We > should have that tested soon using Netty from source, and based on Netty's > release schedule, I expect we would have new Netty (4.0.34) jars before a > RC, maybe even before beta 3. > > - Jim > > On Wed, Jan 13, 2016 at 3:01 PM, Darjus Loktevic <da...@gm...> wrote: > >> 2350 and 2391 should now be cleared. Almost there! >> >> >> >> On Tue, Jan 12, 2016 at 12:42 PM Jim Baker <jim...@py...> wrote: >> >>> Here's my current triage list for beta 3, which are issues that high or >>> urgent in this shortened link: bit.ly/jython-triage-2_7_1: >>> >>> 2350 >>> >>> Installer errors on ensurepip <http://bugs.jython.org/issue2350> >>> >>> 2434 >>> >>> zlib module has different flush behaviour than CPython and PyPy >>> <http://bugs.jython.org/issue2434> >>> >>> 2441 >>> >>> sys.executable is None on standalone install, thus causing a setup() >>> install/build to fail <http://bugs.jython.org/issue2441> >>> >>> 2391 >>> >>> read-only attr wrongly reported <http://bugs.jython.org/issue2391> >>> >>> >>> >>> >>> This is *my* triage list - feel free to respond here if you think there >>> are bugs that should be resolved in beta 3. >>> >>> In parallel work, Darjus has a branch that should resolve setuptools >>> issues in http://bugs.jython.org/issue2360. We will be testing that >>> shortly. I believe that change also has a dependency, via urllib3, on >>> http://bugs.jython.org/issue2434, so I have bumped that priority to >>> urgent (= blocking) accordingly. >>> >>> Except for #2434, we have proposed fixes for all issues above. But #2434 >>> is also quite straightforward. So I expect that in the next week or less we >>> will have everything we need for beta 3. >>> >>> The remaining issues that are listed as normal in the triage list are >>> ones we might get done in beta 3; or possibly in the RC - they seem low >>> risk bug fixes. Otherwise we can address in 2.7.2. >>> >>> Crossing fingers! >>> >>> - Jim >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >> > |
From: Jim B. <jim...@py...> - 2016-01-13 23:21:47
|
Agreed about almost being there! After further investigation, the zlib fixes look straightforward; these fixes will also include support for the gzip compression, which is tested as part of the urllib3 test suite. There was some recent activity on http://bugs.jython.org/issue2401 It was interesting to be writing up commentary about this on the Netty Google Group thread while Netty was simultaneously releasing a bug fix... We should have that tested soon using Netty from source, and based on Netty's release schedule, I expect we would have new Netty (4.0.34) jars before a RC, maybe even before beta 3. - Jim On Wed, Jan 13, 2016 at 3:01 PM, Darjus Loktevic <da...@gm...> wrote: > 2350 and 2391 should now be cleared. Almost there! > > > > On Tue, Jan 12, 2016 at 12:42 PM Jim Baker <jim...@py...> wrote: > >> Here's my current triage list for beta 3, which are issues that high or >> urgent in this shortened link: bit.ly/jython-triage-2_7_1: >> >> 2350 >> >> Installer errors on ensurepip <http://bugs.jython.org/issue2350> >> >> 2434 >> >> zlib module has different flush behaviour than CPython and PyPy >> <http://bugs.jython.org/issue2434> >> >> 2441 >> >> sys.executable is None on standalone install, thus causing a setup() >> install/build to fail <http://bugs.jython.org/issue2441> >> >> 2391 >> >> read-only attr wrongly reported <http://bugs.jython.org/issue2391> >> >> >> >> >> This is *my* triage list - feel free to respond here if you think there >> are bugs that should be resolved in beta 3. >> >> In parallel work, Darjus has a branch that should resolve setuptools >> issues in http://bugs.jython.org/issue2360. We will be testing that >> shortly. I believe that change also has a dependency, via urllib3, on >> http://bugs.jython.org/issue2434, so I have bumped that priority to >> urgent (= blocking) accordingly. >> >> Except for #2434, we have proposed fixes for all issues above. But #2434 >> is also quite straightforward. So I expect that in the next week or less we >> will have everything we need for beta 3. >> >> The remaining issues that are listed as normal in the triage list are >> ones we might get done in beta 3; or possibly in the RC - they seem low >> risk bug fixes. Otherwise we can address in 2.7.2. >> >> Crossing fingers! >> >> - Jim >> >> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > |
From: Darjus L. <da...@gm...> - 2016-01-13 22:01:52
|
2350 and 2391 should now be cleared. Almost there! On Tue, Jan 12, 2016 at 12:42 PM Jim Baker <jim...@py...> wrote: > Here's my current triage list for beta 3, which are issues that high or > urgent in this shortened link: bit.ly/jython-triage-2_7_1: > > 2350 > > Installer errors on ensurepip <http://bugs.jython.org/issue2350> > > 2434 > > zlib module has different flush behaviour than CPython and PyPy > <http://bugs.jython.org/issue2434> > > 2441 > > sys.executable is None on standalone install, thus causing a setup() > install/build to fail <http://bugs.jython.org/issue2441> > > 2391 > > read-only attr wrongly reported <http://bugs.jython.org/issue2391> > > > > > This is *my* triage list - feel free to respond here if you think there > are bugs that should be resolved in beta 3. > > In parallel work, Darjus has a branch that should resolve setuptools > issues in http://bugs.jython.org/issue2360. We will be testing that > shortly. I believe that change also has a dependency, via urllib3, on > http://bugs.jython.org/issue2434, so I have bumped that priority to > urgent (= blocking) accordingly. > > Except for #2434, we have proposed fixes for all issues above. But #2434 > is also quite straightforward. So I expect that in the next week or less we > will have everything we need for beta 3. > > The remaining issues that are listed as normal in the triage list are ones > we might get done in beta 3; or possibly in the RC - they seem low risk bug > fixes. Otherwise we can address in 2.7.2. > > Crossing fingers! > > - Jim > > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Angel M. <ang...@gm...> - 2016-01-12 05:04:44
|
Hello Guys! I recently switched my GitHub pages gears from sphinx based to Pelican and I currently use both rST and Markdown to build the site if you want to take a look at the code here which also uses travis ci to rebuild the website once some commit is pushed into the repository, If you need help on this I’ll be more than glad to help (I actually was going to propose some prototype of a website in pelican for jython.org in the next few months you got me!) I always wanted to help in the jython development but I never knew where to start looks like this could be the place right? Hahaha Daniel From: Darjus Loktevic Sent: Monday, January 11, 2016 9:21 PM To: Jim Baker; Fernando Cassia; Jython Developers Cc: jyt...@li... Subject: Re: [Jython-dev] [Jython-users] "Who uses Jython" page SNAFU Or we could use Python based solution: http://blog.getpelican.com/ - haven't used it, but i like that there's support for bot rST and Markdown, and Jinja is a nice template language that i actually know :) Saying all that, I love the idea of moving to Github pages. Let's do it!!! Darjus On Tue, Jan 12, 2016 at 2:49 PM Jim Baker <jim...@py...> wrote: Right, we need to provide appropriate metadata on these pages so that search engines ignore these archived pages. To make it easier to do this switch, I'm going to suggest that we move to using jython.github.io, as pointed to by a CNAME from jython.org, so we can start building out our web pages in a way that's more compatible for keeping content timely and relevant. Markdown and Jekyll look quite reasonable to me, in terms of the supporting tooling provided by GitHub. (And I could care less that any of it is powered by Ruby ;) But most importantly this will allow us to take pull requests against the Jython web site content; and maintain the news section using standard blogging. We should also be able to move all Jython wiki information under the same workflow, but that can be done incrementally. It will also depend somewhat if we can mix reStructuredText and Markdown. We recently went through the same migration process for an undergraduate course that I'm teaching this spring (http://csci3155.cs.colorado.edu/), and I found the transition to be reasonably smooth. The good thing is we can get jython.github.io completed first before we make the CNAME switchover. Timing: if this seems like a good idea, we can start this process after we complete 2.7.1 beta 3, hopefully in the next week; and have it switched over in time for 2.7.1 final. - Jim On Thu, Jan 7, 2016 at 2:55 PM, Fernando Cassia <fc...@gm...> wrote: On Thu, Jan 7, 2016 at 4:10 PM, Jim Baker <jim...@py...> wrote: The landing page for that bad link should be https://wiki.python.org/jython/, although perhaps it would be best if it were https://wiki.jython.org As for cgi-bin... I have never touched our static web pages, although I have done some wiki editing periodically. Hopefully someone can take care of this bad link soon! - Jim Thanks Jim, due to the black magic of PageRank, that page comes up as the 2nd result when you google f "Who uses Jython?" https://www.google.com/search?q=who+uses+jython&ie=utf-8&oe=utf-8 FC -- During times of Universal Deceit, telling the truth becomes a revolutionary act Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto Revolucionario - George Orwell ------------------------------------------------------------------------------ _______________________________________________ Jython-users mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-users ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140_______________________________________________ Jython-dev mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-dev |
From: Darjus L. <da...@gm...> - 2016-01-12 04:20:44
|
Or we could use Python based solution: http://blog.getpelican.com/ - haven't used it, but i like that there's support for bot rST and Markdown, and Jinja is a nice template language that i actually know :) Saying all that, I love the idea of moving to Github pages. Let's do it!!! Darjus On Tue, Jan 12, 2016 at 2:49 PM Jim Baker <jim...@py...> wrote: > Right, we need to provide appropriate metadata on these pages so that > search engines ignore these archived pages. > > To make it easier to do this switch, I'm going to suggest that we move to > using jython.github.io, as pointed to by a CNAME from jython.org, so we > can start building out our web pages in a way that's more compatible for > keeping content timely and relevant. Markdown and Jekyll look quite > reasonable to me, in terms of the supporting tooling provided by GitHub. > (And I could care less that any of it is powered by Ruby ;) But most > importantly this will allow us to take pull requests against the Jython web > site content; and maintain the news section using standard blogging. > > We should also be able to move all Jython wiki information under the same > workflow, but that can be done incrementally. It will also depend somewhat > if we can mix reStructuredText and Markdown. > > We recently went through the same migration process for an undergraduate > course that I'm teaching this spring (http://csci3155.cs.colorado.edu/), > and I found the transition to be reasonably smooth. The good thing is we > can get jython.github.io completed first before we make the CNAME > switchover. > > Timing: if this seems like a good idea, we can start this process after we > complete 2.7.1 beta 3, hopefully in the next week; and have it switched > over in time for 2.7.1 final. > > - Jim > > On Thu, Jan 7, 2016 at 2:55 PM, Fernando Cassia <fc...@gm...> wrote: > >> >> On Thu, Jan 7, 2016 at 4:10 PM, Jim Baker <jim...@py...> wrote: >> >>> The landing page for that bad link should be >>> https://wiki.python.org/jython/, although perhaps it would be best if >>> it were https://wiki.jython.org >>> >>> As for cgi-bin... >>> >>> I have never touched our static web pages, although I have done some >>> wiki editing periodically. Hopefully someone can take care of this bad link >>> soon! >>> >>> - Jim >>> >> >> Thanks Jim, >> >> due to the black magic of PageRank, that page comes up as the 2nd result >> when you google f "Who uses Jython?" >> >> https://www.google.com/search?q=who+uses+jython&ie=utf-8&oe=utf-8 >> >> FC >> -- >> During times of Universal Deceit, telling the truth becomes a >> revolutionary act >> Durante épocas de Engaño Universal, decir la verdad se convierte en un >> Acto Revolucionario >> - George Orwell >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Jython-users mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-users >> >> > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jim B. <jim...@py...> - 2016-01-12 03:49:13
|
Right, we need to provide appropriate metadata on these pages so that search engines ignore these archived pages. To make it easier to do this switch, I'm going to suggest that we move to using jython.github.io, as pointed to by a CNAME from jython.org, so we can start building out our web pages in a way that's more compatible for keeping content timely and relevant. Markdown and Jekyll look quite reasonable to me, in terms of the supporting tooling provided by GitHub. (And I could care less that any of it is powered by Ruby ;) But most importantly this will allow us to take pull requests against the Jython web site content; and maintain the news section using standard blogging. We should also be able to move all Jython wiki information under the same workflow, but that can be done incrementally. It will also depend somewhat if we can mix reStructuredText and Markdown. We recently went through the same migration process for an undergraduate course that I'm teaching this spring (http://csci3155.cs.colorado.edu/), and I found the transition to be reasonably smooth. The good thing is we can get jython.github.io completed first before we make the CNAME switchover. Timing: if this seems like a good idea, we can start this process after we complete 2.7.1 beta 3, hopefully in the next week; and have it switched over in time for 2.7.1 final. - Jim On Thu, Jan 7, 2016 at 2:55 PM, Fernando Cassia <fc...@gm...> wrote: > > On Thu, Jan 7, 2016 at 4:10 PM, Jim Baker <jim...@py...> wrote: > >> The landing page for that bad link should be >> https://wiki.python.org/jython/, although perhaps it would be best if it >> were https://wiki.jython.org >> >> As for cgi-bin... >> >> I have never touched our static web pages, although I have done some wiki >> editing periodically. Hopefully someone can take care of this bad link soon! >> >> - Jim >> > > Thanks Jim, > > due to the black magic of PageRank, that page comes up as the 2nd result > when you google f "Who uses Jython?" > > https://www.google.com/search?q=who+uses+jython&ie=utf-8&oe=utf-8 > > FC > -- > During times of Universal Deceit, telling the truth becomes a > revolutionary act > Durante épocas de Engaño Universal, decir la verdad se convierte en un > Acto Revolucionario > - George Orwell > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Jython-users mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-users > > |
From: Jim B. <jim...@py...> - 2016-01-12 03:33:18
|
Yaqiang, Sounds good about your progress. I'm looking forward to your changes landing in Jython 2.7.2, which we will finally have a chance to work on quite soon now that we are almost done with beta 3 work. I suggest that you organize your changes as either a diff that you add to a bug or equivalently a pull request against https://github.com/jythontools/jython Otherwise it's very challenging for us to review your changes, although the basic outline of what you have done looks good. The other challenge will be to come up with good unit tests so we can verify your fixes. In general, Py.newStringOrUnicode() usually works, because Python 2.7 - and consequently, Jython 2.7 as an implementation - is loose about it works with str and unicode objects and their combination. (Making this more strict is one of the biggest changes in Python 3.) However, I do know that one bug you might encounter, http://bugs.jython.org/issue2295, is going to be hard for us to fix. - Jim On Sat, Jan 9, 2016 at 1:38 AM, yaq...@gm... < yaq...@gm...> wrote: > Jim, > > I have tried revised some code of Jython as below: > > PySystemState.java > > private static void initRegistry(Properties preProperties, Properties postProperties, > boolean standalone, String jarFileName) > PySystemState.prefix = Py.newString(prefix); > to > PySystemState.prefix = Py.newStringOrUnicode(prefix); > > PySystemState.exec_prefix = Py.newString(exec_prefix); > to > PySystemState.exec_prefix = Py.newStringOrUnicode(exec_prefix); > > private static void addPaths(PyList path, String pypath) > path.append(new PyString(tok.nextToken().trim())); > to > path.append(Py.newStringOrUnicode(tok.nextToken().trim())); > > > private static PyList initPath(Properties props, boolean standalone, String jarFileName) > path.append(new PyString(libpath)); > to > path.append(Py.newStringOrUnicode(libpath)); > > PyObject.java > public PyObject __finditem__(String key) > return __finditem__(new PyString(key)); > to > return __finditem__(Py.newStringOrUnicode(key)); > > public void __setitem__(String key, PyObject value) > __setitem__(new PyString(key), value); > to > __setitem__(Py.newStringOrUnicode(key), value); > > zipimporter.java > private void readZipFile(ZipFile zipFile, PyObject files) > PyObject __file__ = new PyString(archive + File.separator + name); > to > PyObject __file__ = Py.newStringOrUnicode(archive + File.separator + name); > > files.__setitem__(new PyString(name), entry); > to > files.__setitem__(Py.newStringOrUnicode(name), entry); > > imp.java > > public static PyObject createFromCode(String name, PyCode c, String moduleLocation) > module.__setattr__("__file__", new PyString(moduleLocation)); > to > module.__setattr__("__file__", Py.newStringOrUnicode(moduleLocation)); > > Now Jython can be initialized with non-ASCII (such as Chinese) characters > in the path. There is still a problem that the Jython module can not be > loaded with non-ASCIIcharacters path. I don't know how to fix it. Can you > give me some clues on it? Thanks. > > Regards > Yaqiang > ------------------------------ > ************************************************* > Dr. Yaqiang Wang > Chinese Academy of Meteorological Sciences (CAMS) > 46, Zhong-Guan-Cun South Avenue > Beijing, 100081 > China > > yaq...@gm... > > http://www.meteothinker.com > *https://www.researchgate.net/profile/Yaqiang_Wang5 > <https://www.researchgate.net/profile/Yaqiang_Wang5>* > ************************************************** > > > *From:* Jim Baker <jim...@py...> > *Date:* 2016-01-09 11:36 > *To:* yaq...@gm... > *CC:* jython-users <jyt...@li...>; Jython Developers > <jyt...@li...> > *Subject:* Re: Re: [Jython-users] How to build Jython standalone jar from > source code > Yaqiang, > > I believe that bug was fixed related to sockets was most likely fixed, but > we have other issues where Java is using Unicode, but Python wants a str > (which is just bytes). So we see it in the somewhat related bugs > http://bugs.jython.org/issue2369 and http://bugs.jython.org/issue2293 > (possibly others). > > I think the only way we are going to solve this problem is for one of us > developers to attempt to do everything using a username/home directory that > does not use ascii. Otherwise we are just doing piecemeal fixes. > > - Jim > > On Fri, Jan 8, 2016 at 8:06 PM, yaq...@gm... < > yaq...@gm...> wrote: > >> Dear jim, >> >> I have built Jython standalone jar for version 2.7.1b2 succesfully using >> 'ant all-jars' command with Java 7. But I still have below problem with >> newest Jython version. >> >> I am developing MeteoInfoLab software using Java and Jython (as script >> language). It's ok to initialize Jython when the directory path only >> includes ASCII characters. But the initialization will be failed if the >> path includes non-ASCII characters (in my case is Chinese characters). The >> error message shows: java.lang.IllegalArgumentException: Cannot create PyString with non-byte value. >> The issue 2331 said it has been solved in 2.7.1b2 ( >> http://bugs.jython.org/issue2331) , but the problem is still there from >> my test. I also mentioned that a comment report same problem in github ( >> https://github.com/jythontools/jython/commit/c61eaefb774cdb174472265d3c27fc5b87febd34 >> ). >> >> The detailed error message: >> >> java.lang.IllegalArgumentException: Cannot create PyString with non-byte value >> at org.python.core.PyString.<init>(PyString.java:64) >> at org.python.core.PyString.<init>(PyString.java:70) >> at org.python.core.Py.newString(Py.java:645) >> at org.python.core.PySystemState.initRegistry(PySystemState.java:795) >> at org.python.core.PySystemState.doInitialize(PySystemState.java:1040) >> at org.python.core.PySystemState.initialize(PySystemState.java:969) >> at org.python.core.PySystemState.initialize(PySystemState.java:925) >> at org.python.core.PySystemState.initialize(PySystemState.java:920) >> at org.python.core.PySystemState.initialize(PySystemState.java:915) >> at org.python.core.PySystemState.initialize(PySystemState.java:911) >> >> at org.python.core.ThreadStateMapping.getThreadState(ThreadStateMapping.java:32) >> at org.python.core.Py.getThreadState(Py.java:1457) >> at org.python.core.Py.getThreadState(Py.java:1453) >> at org.python.core.Py.getSystemState(Py.java:1473) >> >> at org.meteoinfo.laboratory.gui.ConsoleDockable.initializeConsole(ConsoleDockable.java:65) >> >> at org.meteoinfo.laboratory.gui.ConsoleDockable.<init>(ConsoleDockable.java:47) >> at org.meteoinfo.laboratory.gui.FrmMain.<init>(FrmMain.java:143) >> at org.meteoinfo.laboratory.MeteoInfoLab$1.run(MeteoInfoLab.java:264) >> >> Regards >> Yaqiang >> ------------------------------ >> ************************************************* >> Dr. Yaqiang Wang >> Chinese Academy of Meteorological Sciences (CAMS) >> 46, Zhong-Guan-Cun South Avenue >> Beijing, 100081 >> China >> >> yaq...@gm... >> >> http://www.meteothinker.com >> *https://www.researchgate.net/profile/Yaqiang_Wang5 >> <https://www.researchgate.net/profile/Yaqiang_Wang5>* >> ************************************************** >> >> >> *From:* Jim Baker <jim...@py...> >> *Date:* 2016-01-09 10:10 >> *To:* yaq...@gm... >> *CC:* jython-users <jyt...@li...> >> *Subject:* Re: [Jython-users] How to build Jython standalone jar from >> source code >> Yaqiang, >> >> Check out the source from https://hg.python.org/jython or the mirror at >> https://github.com/jythontools/jython >> >> You can build from source by using this ant target: >> >> all all-jars >> >> The standalone jar is in dist/jython-standalone.jar >> >> Please note that due to the use of an older version of Antlr, building is >> only currently supported on Java 7; but built jars will run on Java 7, 8, >> or 9. (Taking into account this limitation with Java 9: >> http://bugs.jython.org/issue2362) >> >> Hope this helps! >> >> - Jim >> >> On Fri, Jan 8, 2016 at 7:02 PM, yaq...@gm... < >> yaq...@gm...> wrote: >> >>> How to build Jython standalone jar from source code? Any help is >>> appreciated. >>> >>> Regrads >>> Yaqiang >>> ------------------------------ >>> ************************************************* >>> Dr. Yaqiang Wang >>> Chinese Academy of Meteorological Sciences (CAMS) >>> 46, Zhong-Guan-Cun South Avenue >>> Beijing, 100081 >>> China >>> >>> yaq...@gm... >>> >>> http://www.meteothinker.com >>> *https://www.researchgate.net/profile/Yaqiang_Wang5 >>> <https://www.researchgate.net/profile/Yaqiang_Wang5>* >>> ************************************************** >>> >>> >>> ------------------------------------------------------------------------------ >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 >>> _______________________________________________ >>> Jython-users mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-users >>> >>> >> > |
From: Jim B. <jim...@py...> - 2016-01-12 01:41:28
|
Here's my current triage list for beta 3, which are issues that high or urgent in this shortened link: bit.ly/jython-triage-2_7_1: 2350 Installer errors on ensurepip <http://bugs.jython.org/issue2350> 2434 zlib module has different flush behaviour than CPython and PyPy <http://bugs.jython.org/issue2434> 2441 sys.executable is None on standalone install, thus causing a setup() install/build to fail <http://bugs.jython.org/issue2441> 2391 read-only attr wrongly reported <http://bugs.jython.org/issue2391> This is *my* triage list - feel free to respond here if you think there are bugs that should be resolved in beta 3. In parallel work, Darjus has a branch that should resolve setuptools issues in http://bugs.jython.org/issue2360. We will be testing that shortly. I believe that change also has a dependency, via urllib3, on http://bugs.jython.org/issue2434, so I have bumped that priority to urgent (= blocking) accordingly. Except for #2434, we have proposed fixes for all issues above. But #2434 is also quite straightforward. So I expect that in the next week or less we will have everything we need for beta 3. The remaining issues that are listed as normal in the triage list are ones we might get done in beta 3; or possibly in the RC - they seem low risk bug fixes. Otherwise we can address in 2.7.2. Crossing fingers! - Jim |
From: <yaq...@gm...> - 2016-01-09 08:38:46
|
Jim, I have tried revised some code of Jython as below: PySystemState.java private static void initRegistry(Properties preProperties, Properties postProperties, boolean standalone, String jarFileName) PySystemState.prefix = Py.newString(prefix); to PySystemState.prefix = Py.newStringOrUnicode(prefix); PySystemState.exec_prefix = Py.newString(exec_prefix); to PySystemState.exec_prefix = Py.newStringOrUnicode(exec_prefix); private static void addPaths(PyList path, String pypath) path.append(new PyString(tok.nextToken().trim())); to path.append(Py.newStringOrUnicode(tok.nextToken().trim())); private static PyList initPath(Properties props, boolean standalone, String jarFileName) path.append(new PyString(libpath)); to path.append(Py.newStringOrUnicode(libpath)); PyObject.java public PyObject __finditem__(String key) return __finditem__(new PyString(key)); to return __finditem__(Py.newStringOrUnicode(key)); public void __setitem__(String key, PyObject value) __setitem__(new PyString(key), value); to __setitem__(Py.newStringOrUnicode(key), value); zipimporter.java private void readZipFile(ZipFile zipFile, PyObject files) PyObject __file__ = new PyString(archive + File.separator + name); to PyObject __file__ = Py.newStringOrUnicode(archive + File.separator + name); files.__setitem__(new PyString(name), entry); to files.__setitem__(Py.newStringOrUnicode(name), entry); imp.java public static PyObject createFromCode(String name, PyCode c, String moduleLocation) module.__setattr__("__file__", new PyString(moduleLocation)); to module.__setattr__("__file__", Py.newStringOrUnicode(moduleLocation)); Now Jython can be initialized with non-ASCII (such as Chinese) characters in the path. There is still a problem that the Jython module can not be loaded with non-ASCIIcharacters path. I don't know how to fix it. Can you give me some clues on it? Thanks. Regards Yaqiang ************************************************* Dr. Yaqiang Wang Chinese Academy of Meteorological Sciences (CAMS) 46, Zhong-Guan-Cun South Avenue Beijing, 100081 China yaq...@gm... http://www.meteothinker.com https://www.researchgate.net/profile/Yaqiang_Wang5 ************************************************** From: Jim Baker Date: 2016-01-09 11:36 To: yaq...@gm... CC: jython-users; Jython Developers Subject: Re: Re: [Jython-users] How to build Jython standalone jar from source code Yaqiang, I believe that bug was fixed related to sockets was most likely fixed, but we have other issues where Java is using Unicode, but Python wants a str (which is just bytes). So we see it in the somewhat related bugs http://bugs.jython.org/issue2369 and http://bugs.jython.org/issue2293 (possibly others). I think the only way we are going to solve this problem is for one of us developers to attempt to do everything using a username/home directory that does not use ascii. Otherwise we are just doing piecemeal fixes. - Jim On Fri, Jan 8, 2016 at 8:06 PM, yaq...@gm... <yaq...@gm...> wrote: Dear jim, I have built Jython standalone jar for version 2.7.1b2 succesfully using 'ant all-jars' command with Java 7. But I still have below problem with newest Jython version. I am developing MeteoInfoLab software using Java and Jython (as script language). It's ok to initialize Jython when the directory path only includes ASCII characters. But the initialization will be failed if the path includes non-ASCII characters (in my case is Chinese characters). The error message shows: java.lang.IllegalArgumentException: Cannot create PyString with non-byte value. The issue 2331 said it has been solved in 2.7.1b2 (http://bugs.jython.org/issue2331) , but the problem is still there from my test. I also mentioned that a comment report same problem in github (https://github.com/jythontools/jython/commit/c61eaefb774cdb174472265d3c27fc5b87febd34). The detailed error message: java.lang.IllegalArgumentException: Cannot create PyString with non-byte value at org.python.core.PyString.<init>(PyString.java:64) at org.python.core.PyString.<init>(PyString.java:70) at org.python.core.Py.newString(Py.java:645) at org.python.core.PySystemState.initRegistry(PySystemState.java:795) at org.python.core.PySystemState.doInitialize(PySystemState.java:1040) at org.python.core.PySystemState.initialize(PySystemState.java:969) at org.python.core.PySystemState.initialize(PySystemState.java:925) at org.python.core.PySystemState.initialize(PySystemState.java:920) at org.python.core.PySystemState.initialize(PySystemState.java:915) at org.python.core.PySystemState.initialize(PySystemState.java:911) at org.python.core.ThreadStateMapping.getThreadState(ThreadStateMapping.java:32) at org.python.core.Py.getThreadState(Py.java:1457) at org.python.core.Py.getThreadState(Py.java:1453) at org.python.core.Py.getSystemState(Py.java:1473) at org.meteoinfo.laboratory.gui.ConsoleDockable.initializeConsole(ConsoleDockable.java:65) at org.meteoinfo.laboratory.gui.ConsoleDockable.<init>(ConsoleDockable.java:47) at org.meteoinfo.laboratory.gui.FrmMain.<init>(FrmMain.java:143) at org.meteoinfo.laboratory.MeteoInfoLab$1.run(MeteoInfoLab.java:264) Regards Yaqiang ************************************************* Dr. Yaqiang Wang Chinese Academy of Meteorological Sciences (CAMS) 46, Zhong-Guan-Cun South Avenue Beijing, 100081 China yaq...@gm... http://www.meteothinker.com https://www.researchgate.net/profile/Yaqiang_Wang5 ************************************************** From: Jim Baker Date: 2016-01-09 10:10 To: yaq...@gm... CC: jython-users Subject: Re: [Jython-users] How to build Jython standalone jar from source code Yaqiang, Check out the source from https://hg.python.org/jython or the mirror at https://github.com/jythontools/jython You can build from source by using this ant target: all all-jars The standalone jar is in dist/jython-standalone.jar Please note that due to the use of an older version of Antlr, building is only currently supported on Java 7; but built jars will run on Java 7, 8, or 9. (Taking into account this limitation with Java 9: http://bugs.jython.org/issue2362) Hope this helps! - Jim On Fri, Jan 8, 2016 at 7:02 PM, yaq...@gm... <yaq...@gm...> wrote: How to build Jython standalone jar from source code? Any help is appreciated. Regrads Yaqiang ************************************************* Dr. Yaqiang Wang Chinese Academy of Meteorological Sciences (CAMS) 46, Zhong-Guan-Cun South Avenue Beijing, 100081 China yaq...@gm... http://www.meteothinker.com https://www.researchgate.net/profile/Yaqiang_Wang5 ************************************************** ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Jython-users mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-users |
From: <yaq...@gm...> - 2016-01-09 04:12:37
|
Jim, I am trying to solve the problem from source code of Jython. I think all 'new PyString(str)' and 'Py.newString(str) functions should be replaced by 'Py.newStringOrUnicode(str)' function. But it seems 'PyObject.java' content can not be changed. For example, I changed public PyObject __finditem__(String key) { return __finditem__(new PyString(key)); } to public PyObject __finditem__(String key) { return __finditem__(Py.newStringOrUnicode(key)); } But after source code building the content of 'PyObject.java' was changed automaticlly to original content. How to solve it? Regards Yaqiang ************************************************* Dr. Yaqiang Wang Chinese Academy of Meteorological Sciences (CAMS) 46, Zhong-Guan-Cun South Avenue Beijing, 100081 China yaq...@gm... http://www.meteothinker.com https://www.researchgate.net/profile/Yaqiang_Wang5 ************************************************** From: Jim Baker Date: 2016-01-09 11:36 To: yaq...@gm... CC: jython-users; Jython Developers Subject: Re: Re: [Jython-users] How to build Jython standalone jar from source code Yaqiang, I believe that bug was fixed related to sockets was most likely fixed, but we have other issues where Java is using Unicode, but Python wants a str (which is just bytes). So we see it in the somewhat related bugs http://bugs.jython.org/issue2369 and http://bugs.jython.org/issue2293 (possibly others). I think the only way we are going to solve this problem is for one of us developers to attempt to do everything using a username/home directory that does not use ascii. Otherwise we are just doing piecemeal fixes. - Jim On Fri, Jan 8, 2016 at 8:06 PM, yaq...@gm... <yaq...@gm...> wrote: Dear jim, I have built Jython standalone jar for version 2.7.1b2 succesfully using 'ant all-jars' command with Java 7. But I still have below problem with newest Jython version. I am developing MeteoInfoLab software using Java and Jython (as script language). It's ok to initialize Jython when the directory path only includes ASCII characters. But the initialization will be failed if the path includes non-ASCII characters (in my case is Chinese characters). The error message shows: java.lang.IllegalArgumentException: Cannot create PyString with non-byte value. The issue 2331 said it has been solved in 2.7.1b2 (http://bugs.jython.org/issue2331) , but the problem is still there from my test. I also mentioned that a comment report same problem in github (https://github.com/jythontools/jython/commit/c61eaefb774cdb174472265d3c27fc5b87febd34). The detailed error message: java.lang.IllegalArgumentException: Cannot create PyString with non-byte value at org.python.core.PyString.<init>(PyString.java:64) at org.python.core.PyString.<init>(PyString.java:70) at org.python.core.Py.newString(Py.java:645) at org.python.core.PySystemState.initRegistry(PySystemState.java:795) at org.python.core.PySystemState.doInitialize(PySystemState.java:1040) at org.python.core.PySystemState.initialize(PySystemState.java:969) at org.python.core.PySystemState.initialize(PySystemState.java:925) at org.python.core.PySystemState.initialize(PySystemState.java:920) at org.python.core.PySystemState.initialize(PySystemState.java:915) at org.python.core.PySystemState.initialize(PySystemState.java:911) at org.python.core.ThreadStateMapping.getThreadState(ThreadStateMapping.java:32) at org.python.core.Py.getThreadState(Py.java:1457) at org.python.core.Py.getThreadState(Py.java:1453) at org.python.core.Py.getSystemState(Py.java:1473) at org.meteoinfo.laboratory.gui.ConsoleDockable.initializeConsole(ConsoleDockable.java:65) at org.meteoinfo.laboratory.gui.ConsoleDockable.<init>(ConsoleDockable.java:47) at org.meteoinfo.laboratory.gui.FrmMain.<init>(FrmMain.java:143) at org.meteoinfo.laboratory.MeteoInfoLab$1.run(MeteoInfoLab.java:264) Regards Yaqiang ************************************************* Dr. Yaqiang Wang Chinese Academy of Meteorological Sciences (CAMS) 46, Zhong-Guan-Cun South Avenue Beijing, 100081 China yaq...@gm... http://www.meteothinker.com https://www.researchgate.net/profile/Yaqiang_Wang5 ************************************************** From: Jim Baker Date: 2016-01-09 10:10 To: yaq...@gm... CC: jython-users Subject: Re: [Jython-users] How to build Jython standalone jar from source code Yaqiang, Check out the source from https://hg.python.org/jython or the mirror at https://github.com/jythontools/jython You can build from source by using this ant target: all all-jars The standalone jar is in dist/jython-standalone.jar Please note that due to the use of an older version of Antlr, building is only currently supported on Java 7; but built jars will run on Java 7, 8, or 9. (Taking into account this limitation with Java 9: http://bugs.jython.org/issue2362) Hope this helps! - Jim On Fri, Jan 8, 2016 at 7:02 PM, yaq...@gm... <yaq...@gm...> wrote: How to build Jython standalone jar from source code? Any help is appreciated. Regrads Yaqiang ************************************************* Dr. Yaqiang Wang Chinese Academy of Meteorological Sciences (CAMS) 46, Zhong-Guan-Cun South Avenue Beijing, 100081 China yaq...@gm... http://www.meteothinker.com https://www.researchgate.net/profile/Yaqiang_Wang5 ************************************************** ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Jython-users mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-users |
From: Jim B. <jim...@py...> - 2016-01-09 03:36:32
|
Yaqiang, I believe that bug was fixed related to sockets was most likely fixed, but we have other issues where Java is using Unicode, but Python wants a str (which is just bytes). So we see it in the somewhat related bugs http://bugs.jython.org/issue2369 and http://bugs.jython.org/issue2293 (possibly others). I think the only way we are going to solve this problem is for one of us developers to attempt to do everything using a username/home directory that does not use ascii. Otherwise we are just doing piecemeal fixes. - Jim On Fri, Jan 8, 2016 at 8:06 PM, yaq...@gm... < yaq...@gm...> wrote: > Dear jim, > > I have built Jython standalone jar for version 2.7.1b2 succesfully using > 'ant all-jars' command with Java 7. But I still have below problem with > newest Jython version. > > I am developing MeteoInfoLab software using Java and Jython (as script > language). It's ok to initialize Jython when the directory path only > includes ASCII characters. But the initialization will be failed if the > path includes non-ASCII characters (in my case is Chinese characters). The > error message shows: java.lang.IllegalArgumentException: Cannot create PyString with non-byte value. > The issue 2331 said it has been solved in 2.7.1b2 ( > http://bugs.jython.org/issue2331) , but the problem is still there from > my test. I also mentioned that a comment report same problem in github ( > https://github.com/jythontools/jython/commit/c61eaefb774cdb174472265d3c27fc5b87febd34 > ). > > The detailed error message: > > java.lang.IllegalArgumentException: Cannot create PyString with non-byte value > at org.python.core.PyString.<init>(PyString.java:64) > at org.python.core.PyString.<init>(PyString.java:70) > at org.python.core.Py.newString(Py.java:645) > at org.python.core.PySystemState.initRegistry(PySystemState.java:795) > at org.python.core.PySystemState.doInitialize(PySystemState.java:1040) > at org.python.core.PySystemState.initialize(PySystemState.java:969) > at org.python.core.PySystemState.initialize(PySystemState.java:925) > at org.python.core.PySystemState.initialize(PySystemState.java:920) > at org.python.core.PySystemState.initialize(PySystemState.java:915) > at org.python.core.PySystemState.initialize(PySystemState.java:911) > > at org.python.core.ThreadStateMapping.getThreadState(ThreadStateMapping.java:32) > at org.python.core.Py.getThreadState(Py.java:1457) > at org.python.core.Py.getThreadState(Py.java:1453) > at org.python.core.Py.getSystemState(Py.java:1473) > > at org.meteoinfo.laboratory.gui.ConsoleDockable.initializeConsole(ConsoleDockable.java:65) > > at org.meteoinfo.laboratory.gui.ConsoleDockable.<init>(ConsoleDockable.java:47) > at org.meteoinfo.laboratory.gui.FrmMain.<init>(FrmMain.java:143) > at org.meteoinfo.laboratory.MeteoInfoLab$1.run(MeteoInfoLab.java:264) > > Regards > Yaqiang > ------------------------------ > ************************************************* > Dr. Yaqiang Wang > Chinese Academy of Meteorological Sciences (CAMS) > 46, Zhong-Guan-Cun South Avenue > Beijing, 100081 > China > > yaq...@gm... > > http://www.meteothinker.com > *https://www.researchgate.net/profile/Yaqiang_Wang5 > <https://www.researchgate.net/profile/Yaqiang_Wang5>* > ************************************************** > > > *From:* Jim Baker <jim...@py...> > *Date:* 2016-01-09 10:10 > *To:* yaq...@gm... > *CC:* jython-users <jyt...@li...> > *Subject:* Re: [Jython-users] How to build Jython standalone jar from > source code > Yaqiang, > > Check out the source from https://hg.python.org/jython or the mirror at > https://github.com/jythontools/jython > > You can build from source by using this ant target: > > all all-jars > > The standalone jar is in dist/jython-standalone.jar > > Please note that due to the use of an older version of Antlr, building is > only currently supported on Java 7; but built jars will run on Java 7, 8, > or 9. (Taking into account this limitation with Java 9: > http://bugs.jython.org/issue2362) > > Hope this helps! > > - Jim > > On Fri, Jan 8, 2016 at 7:02 PM, yaq...@gm... < > yaq...@gm...> wrote: > >> How to build Jython standalone jar from source code? Any help is >> appreciated. >> >> Regrads >> Yaqiang >> ------------------------------ >> ************************************************* >> Dr. Yaqiang Wang >> Chinese Academy of Meteorological Sciences (CAMS) >> 46, Zhong-Guan-Cun South Avenue >> Beijing, 100081 >> China >> >> yaq...@gm... >> >> http://www.meteothinker.com >> *https://www.researchgate.net/profile/Yaqiang_Wang5 >> <https://www.researchgate.net/profile/Yaqiang_Wang5>* >> ************************************************** >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 >> _______________________________________________ >> Jython-users mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-users >> >> > |
From: Jython t. <st...@bu...> - 2016-01-08 17:10:21
|
ACTIVITY SUMMARY (2016-01-01 - 2016-01-08) 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 273 ( -4) closed 2197 ( +6) total 2470 ( +2) Open issues with patches: 27 Issues opened (1) ================= #2451: array.array objects should not hash http://bugs.jython.org/issue2451 opened by lsenta Most recent 15 issues with no replies (15) ========================================== #2447: Support server-side STARTTLS for SSL http://bugs.jython.org/issue2447 #2446: Support SNI for SSL/TLS http://bugs.jython.org/issue2446 #2443: java.util.Map derived classes lack iterkeys, itervalues method http://bugs.jython.org/issue2443 #2434: zlib module has different flush behaviour than CPython and PyP http://bugs.jython.org/issue2434 #2422: test_classpathimporter fauls on Linux http://bugs.jython.org/issue2422 #2418: test_chdir subprocess tests fail on Windows http://bugs.jython.org/issue2418 #2410: Regression in PySystemStateTest (leading slash) http://bugs.jython.org/issue2410 #2408: Redo sre port for regular expression support http://bugs.jython.org/issue2408 #2395: Parser bug with unparenthesized genexp with star-args http://bugs.jython.org/issue2395 #2378: Current docs aren't. http://bugs.jython.org/issue2378 #2369: running jython-standalone.jar in desktops with with korean lan http://bugs.jython.org/issue2369 #2363: relative seeks works incorrectly after readline http://bugs.jython.org/issue2363 #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 Most recent 15 issues waiting for review (15) ============================================= #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 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #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 #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 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1767: Rich comparisons http://bugs.jython.org/issue1767 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 #1646: Proxy getInterface not change for more PyObject http://bugs.jython.org/issue1646 Top 10 most discussed issues (5) ================================ #2423: jarray.array() method broken in 2.7 http://bugs.jython.org/issue2423 4 msgs #2449: requests library causes memory leak and 100% GC time when hand http://bugs.jython.org/issue2449 4 msgs #2451: array.array objects should not hash http://bugs.jython.org/issue2451 4 msgs #2154: When running multiple engines in different threads, the last r http://bugs.jython.org/issue2154 3 msgs #2360: Not installing pip on Jython http://bugs.jython.org/issue2360 3 msgs Issues closed (1) ================= #2450: Support pympler.muppy for memory leak analysis http://bugs.jython.org/issue2450 closed by darjus |
From: Pekka K. <pe...@ik...> - 2016-01-08 12:37:01
|
2016-01-03 12:14 GMT+02:00 Darjus Loktevic <da...@gm...>: > > Personally i don't mind moving issues to github (not sure we can actually > move them), but i would hate for us to lose all the years of history. We > need to discuss this internally, though i think we should follow what > CPython is doing. I would also prefer GitHub tracker. It's not the best tracker I've used, but I consider it a lot better than Roundup, and it obviously has the best GitHub integration possible. If I've understood it correctly, the main reason it won't be used with CPython are vendor lock-in related. I doubt are such worries relevant with Jython, and in the worst case GitHub APIs allow getting the issue data at least in some format. I understand the value for Jython using same the process than CPython, though. I have promised earlier on IRC and when I met with Jim last spring in Colorado, that I can help migrating existing issues from Roundup to GitHub if we decide to fully move Jython to GitHub. I've done similar migration when we moved Robot Framework from Google Code to GitHub. Due to being busy with work and family I didn't have time to look at that last autumn, but I ought to have time for it now if needed. Cheers, .peke -- Agile Tester/Developer/Consultant :: http://eliga.fi Lead Developer of Robot Framework :: http://robotframework.org |
From: Jim B. <jim...@py...> - 2016-01-07 21:11:03
|
The landing page for that bad link should be https://wiki.python.org/jython/, although perhaps it would be best if it were https://wiki.jython.org As for cgi-bin... I have never touched our static web pages, although I have done some wiki editing periodically. Hopefully someone can take care of this bad link soon! - Jim On Thu, Jan 7, 2016 at 2:02 PM, Fernando Cassia <fc...@gm...> wrote: > http://www.jython.org/archive/21/users.html > Who uses Jython? This page has been retired. Please see JythonUsers > <http://www.jython.org/cgi-bin/wiki/JythonUsers> WIKI page. > > You follow the link and... > > http://www.jython.org/cgi-bin/wiki/JythonUsers > 404 Not Found > ------------------------------ > nginx > FC > > -- > During times of Universal Deceit, telling the truth becomes a > revolutionary act > Durante épocas de Engaño Universal, decir la verdad se convierte en un > Acto Revolucionario > - George Orwell > |
From: Jeff A. <ja...@fa...> - 2016-01-06 21:20:32
|
I subscribed too. This is fine by me, and I see some advantages. I'm very happy to follow the same processes as CPython. And I've been getting to know git while I've been a bit quiet here. Just to be clear ... GitHub *and* using git, I assume. If I read it correctly, moving the bug tracker is not proposed. However, I look forward to learning how that will relate to pull requests and issues managed on GitHub. I don't really want to search multiple places. On the question of "getting control of https://github.com/jython" (Jim's phrase), surely ultimate control of the repo we use should be vested in the PSF, as a trustworthy legal entity likely to outlast any of us. Jeff On 04/01/2016 17:29, fwi...@gm... wrote: > On Sun, Jan 3, 2016 at 8:34 AM, Jim Baker <jim...@py...> wrote: >> Brett, >> >> Thanks for keeping us in the loop! > My thanks as well! I think Jim covered everything on our parallel > plans to move to github. > >> I have subscribed to cor...@py..., and I encourage other >> interested Jython developers to do so. > I have subscribed as well. > > -Frank > > ------------------------------------------------------------------------------ > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: <fwi...@gm...> - 2016-01-04 17:29:56
|
On Sun, Jan 3, 2016 at 8:34 AM, Jim Baker <jim...@py...> wrote: > Brett, > > Thanks for keeping us in the loop! My thanks as well! I think Jim covered everything on our parallel plans to move to github. > I have subscribed to cor...@py..., and I encourage other > interested Jython developers to do so. I have subscribed as well. -Frank |
From: Brett C. <br...@py...> - 2016-01-03 17:09:26
|
On Sun, 3 Jan 2016 at 02:14 Darjus Loktevic <da...@gm...> wrote: > Hey Brett, > > Thanks for the heads up. We've had a github mirror for a little while now, > and "verbally" agreed to move development of Jython3 to github. With the > news of hg.python.org going away, i guess we have no choice but to move > all of Jython to github (personally really like github workflow, but can't > speak for the rest of us). > > I think using jython org would be preferable/easier to manage, thought i > assume we would still want to be covered under PSF contributor agreement > procedure. Would that be a problem if we're not part of the python org (i > doubt it but want to make sure)? > I specifically don't see why it would be a problem, but then again we need to work out that procedure ourselves. :) > > Personally i don't mind moving issues to github (not sure we can actually > move them), but i would hate for us to lose all the years of history. We > need to discuss this internally, though i think we should follow what > CPython is doing. > I'm not saying you have to shut it down, it's just an option if the tweaks we make don't work for you. > > Cheers and Happy New Year! > Same to you! -Brett > Darjus > > On Sun, Jan 3, 2016 at 5:56 AM Brett Cannon <br...@py...> wrote: > >> I wanted to make sure you all are aware that the decision was made by me >> yesterday to move CPython's development to GitHub. This means that >> hg.python.org will most likely be shut down some time in the future. >> Since this decision was reached literally on January 1 there are no >> timelines yet, but my expectation is that hg.python.org and Rietveld >> will be wound down this year (bugs.python.org isn't going anywhere). >> >> I know you host your code on hg.python.org and that you run an instance >> of our issue tracker so I wanted to make sure you were aware of these >> coming changes. I'm not sure if it still makes sense to have you work under >> the python organization on GitHub vs. a jython org and if you want to stick >> to your bugs.python.org clone with the changes we will be making to it, >> but if you want that you can subscribe to cor...@py... and >> discuss it there (people also discussed using GitLab and people suggested >> too late Bitbucket and Rhode Code if you want other options than GitHub if >> you want to know what other options you have). >> > >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > |
From: Jim B. <jim...@py...> - 2016-01-03 16:35:24
|
Brett, Thanks for keeping us in the loop! Sounds good about the switch to GitHub - this is in line with work we have done to-date, including getting control of https://github.com/jython Likely the switch to code management should be a top priority for 2.7.2 development, which should commence sometime in the next month or so (depends on the delayed 2.7.1 getting out first!). We have an outstanding bug, http://bugs.jython.org/issue2182, that needs to be solved first - this will allow us to strip out third-party jars so we are no longer tracking directly in the repo. Once #2182 is taken care of, we can then immediately switch, and for the time being, mirror to hg.python.org/jython. Except for a few cases, we haven't used Rietveld in our review process, so that shutdown doesn't impact us. We of course use bugs.jython.org - it's the essential tool for tracking most dev in Jython - so we don't want that shut down. I'm pretty sure that we would simply want whatever goodness that is being worked on for bugs.python.org applied to our version, especially anything to help review workflows. I have subscribed to cor...@py..., and I encourage other interested Jython developers to do so. - Jim On Sun, Jan 3, 2016 at 3:14 AM, Darjus Loktevic <da...@gm...> wrote: > Hey Brett, > > Thanks for the heads up. We've had a github mirror for a little while now, > and "verbally" agreed to move development of Jython3 to github. With the > news of hg.python.org going away, i guess we have no choice but to move > all of Jython to github (personally really like github workflow, but can't > speak for the rest of us). > > I think using jython org would be preferable/easier to manage, thought i > assume we would still want to be covered under PSF contributor agreement > procedure. Would that be a problem if we're not part of the python org (i > doubt it but want to make sure)? > > Personally i don't mind moving issues to github (not sure we can actually > move them), but i would hate for us to lose all the years of history. We > need to discuss this internally, though i think we should follow what > CPython is doing. > > Cheers and Happy New Year! > Darjus > > On Sun, Jan 3, 2016 at 5:56 AM Brett Cannon <br...@py...> wrote: > >> I wanted to make sure you all are aware that the decision was made by me >> yesterday to move CPython's development to GitHub. This means that >> hg.python.org will most likely be shut down some time in the future. >> Since this decision was reached literally on January 1 there are no >> timelines yet, but my expectation is that hg.python.org and Rietveld >> will be wound down this year (bugs.python.org isn't going anywhere). >> >> I know you host your code on hg.python.org and that you run an instance >> of our issue tracker so I wanted to make sure you were aware of these >> coming changes. I'm not sure if it still makes sense to have you work under >> the python organization on GitHub vs. a jython org and if you want to stick >> to your bugs.python.org clone with the changes we will be making to it, >> but if you want that you can subscribe to cor...@py... and >> discuss it there (people also discussed using GitLab and people suggested >> too late Bitbucket and Rhode Code if you want other options than GitHub if >> you want to know what other options you have). >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > |
From: Darjus L. <da...@gm...> - 2016-01-03 10:14:26
|
Hey Brett, Thanks for the heads up. We've had a github mirror for a little while now, and "verbally" agreed to move development of Jython3 to github. With the news of hg.python.org going away, i guess we have no choice but to move all of Jython to github (personally really like github workflow, but can't speak for the rest of us). I think using jython org would be preferable/easier to manage, thought i assume we would still want to be covered under PSF contributor agreement procedure. Would that be a problem if we're not part of the python org (i doubt it but want to make sure)? Personally i don't mind moving issues to github (not sure we can actually move them), but i would hate for us to lose all the years of history. We need to discuss this internally, though i think we should follow what CPython is doing. Cheers and Happy New Year! Darjus On Sun, Jan 3, 2016 at 5:56 AM Brett Cannon <br...@py...> wrote: > I wanted to make sure you all are aware that the decision was made by me > yesterday to move CPython's development to GitHub. This means that > hg.python.org will most likely be shut down some time in the future. > Since this decision was reached literally on January 1 there are no > timelines yet, but my expectation is that hg.python.org and Rietveld will > be wound down this year (bugs.python.org isn't going anywhere). > > I know you host your code on hg.python.org and that you run an instance > of our issue tracker so I wanted to make sure you were aware of these > coming changes. I'm not sure if it still makes sense to have you work under > the python organization on GitHub vs. a jython org and if you want to stick > to your bugs.python.org clone with the changes we will be making to it, > but if you want that you can subscribe to cor...@py... and > discuss it there (people also discussed using GitLab and people suggested > too late Bitbucket and Rhode Code if you want other options than GitHub if > you want to know what other options you have). > > ------------------------------------------------------------------------------ > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Brett C. <br...@py...> - 2016-01-02 18:55:37
|
I wanted to make sure you all are aware that the decision was made by me yesterday to move CPython's development to GitHub. This means that hg.python.org will most likely be shut down some time in the future. Since this decision was reached literally on January 1 there are no timelines yet, but my expectation is that hg.python.org and Rietveld will be wound down this year (bugs.python.org isn't going anywhere). I know you host your code on hg.python.org and that you run an instance of our issue tracker so I wanted to make sure you were aware of these coming changes. I'm not sure if it still makes sense to have you work under the python organization on GitHub vs. a jython org and if you want to stick to your bugs.python.org clone with the changes we will be making to it, but if you want that you can subscribe to cor...@py... and discuss it there (people also discussed using GitLab and people suggested too late Bitbucket and Rhode Code if you want other options than GitHub if you want to know what other options you have). |