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: Antti H. <an...@ha...> - 2015-06-06 18:58:16
|
Hi all, I'd like to contribute substantially to the Jython 3 development. I am far from a n00b with Java or Python, but I really didn't know anything about the internals of Jython before ~2 weeks ago, thus I'd guess not even of much use with Jython 2.7 development even if I wanted. But Jython 3 changes would be something where I could be quite useful - Alex Grönholm already merged some of my PRs to Jython 3 sandbox. ---- I have made a pull request that introduces PyBytes to Jython 3 - basically what I did was to take the PyByteArray and removed the mutating methods, changed the __repr__, etc. It was suggested that Jeff Allen should review my PyBytes PR at https://github.com/jython/jython3/pull/5/files - so it'd be nice if Jeff you could review it. That commit also makes the compiler to produce bytes literals with b'foo'; the bytes literals would be stored as "latin-1" string constants in .class files. The code "works for me (tm)" in the interactive interpreter. ---- Next, if the PyBytes were be accepted, I was thinking I'd want to try merging PyInteger with PyLong; and PyString with PyUnicode if no one else has it coming yet. However, naming things is still hard. What do you all think the Python 3 str and int should be called on the Java side? CPython 3 still calls them PyUnicode* and PyLong*, which makes sense, since their C-API is consistent with these Python 2 types; and all usages of PyString* and PyInt* should be reviewed for changes when porting extensions to Python 3. ---- Also, I've listed some to-do items in the Github issue tracker; how do you feel about using the Github issue tracker at least for this in the early phase of Jython 3 experimentation? Or should these too be in Roundup? Any thoughts? -- Antti Haapala |
From: Jython t. <st...@bu...> - 2015-06-05 16:10:20
|
ACTIVITY SUMMARY (2015-05-29 - 2015-06-05) 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 249 ( +3) closed 2135 ( -1) total 2384 ( +2) Open issues with patches: 26 Issues opened (3) ================= #2333: ensurepip passwd.pw_passwd unimplemented http://bugs.jython.org/issue2333 reopened by zyasoft #2364: bytearray isalpha behaviour different from Python 2 http://bugs.jython.org/issue2364 opened by ztane #2365: Jython/pip javax.net.ssl.SSLException: handshake timed out http://bugs.jython.org/issue2365 opened by alexgs Most recent 15 issues with no replies (15) ========================================== #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 #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 #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 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #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 #1612: array.array should use specialized bulk operations to initiali http://bugs.jython.org/issue1612 Top 10 most discussed issues (1) ================================ #2365: Jython/pip javax.net.ssl.SSLException: handshake timed out http://bugs.jython.org/issue2365 6 msgs |
From: Rory O'D. <ror...@or...> - 2015-06-05 09:16:46
|
Hi Alan/Jim, Early Access build for JDK 8u60 b18 <http://jdk8.java.net/download.html> is available on java.net, summary of changes are listed here. <http://www.java.net/download/jdk8u60/changes/jdk8u60-b18.html> As we enter the later phases of development for JDK 8u60, please log any show stoppers as soon as possible. Early Access build for JDK 9 b66 <https://jdk9.java.net/download/> is available on java.net, summary of changes are listed here <http://www.java.net/download/jdk9/changes/jdk9-b66.html>. The JDK 9 schedule of record is available on the JDK 9 Project page: http://openjdk.java.net/projects/jdk9 At https://wiki.openjdk.java.net/display/Adoption/JDK+9+Outreach you can find a (preliminary) list of other changes that might affect your project's code in JDK 9, and other things to consider when testing with JDK 9. I'd be curious to know if there is anything on that list you'd consider to have an effect on your project. Please keep in mind that as JEPs and others changes are integrated into (or out of) JDK 9, the list will change over time. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland |
From: Jim B. <jim...@py...> - 2015-06-03 16:32:41
|
Works for me, per my response on http://bugs.jython.org/issue2365: $ ~/jython2.7.0/bin/pip install requests Downloading/unpacking requests Downloading requests-2.7.0-py2.py3-none-any.whl (470kB): 470kB downloaded Installing collected packages: requests Successfully installed requests Cleaning up... There are a number of ways the SSL handshake could go wrong, and we almost certainly need to provide better diagnostic information when it does fail. We could start by systematically testing failures that we can induce, such as testing with a bad CA certificate. It would be helpful if anyone who has seen SSL handshake errors to comment on #2365 so we can systematically determine what failures can be seen. One that I have seen is SSLEngine failures with nonverified certs - this is correct in the sense that it should not work, but it should report a better error. (The solution in that case is to add the cert to the trust store in Java, or to pass it explicitly in the wrap_socket function.) - Jim On Wed, Jun 3, 2015 at 9:55 AM, Alex G.S. <alx...@gm...> wrote: > > Dev List, > > Recently I found about Jython and having done some Java in the past was instantly interested. However upon setting up the JAR file, it appears that pip is not functional due to an SSLException. I've posted a bug about this on the tracker [1]. Is this known issue or is this a configuration issue or a step that I'm missing in setting this up? > > Thank you for whatever assistance you can provide! > > Regards, > Alex > > [1] http://bugs.jython.org/issue2365 > -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |
From: Alex G.S. <alx...@gm...> - 2015-06-03 15:56:30
|
Dev List, Recently I found about Jython and having done some Java in the past was instantly interested. However upon setting up the JAR file, it appears that pip is not functional due to an SSLException. I've posted a bug about this on the tracker [1]. Is this known issue or is this a configuration issue or a step that I'm missing in setting this up? Thank you for whatever assistance you can provide! Regards, Alex [1] http://bugs.jython.org/issue2365 |
From: Jython t. <st...@bu...> - 2015-05-29 16:10:20
|
ACTIVITY SUMMARY (2015-05-22 - 2015-05-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 246 ( +2) closed 2136 ( +3) total 2382 ( +5) Open issues with patches: 26 Issues opened (5) ================= #2359: Many Java-defined functions do not accept keyword arguments http://bugs.jython.org/issue2359 opened by jdemoor #2360: Not installing pip on Jython http://bugs.jython.org/issue2360 opened by thavihaz909 #2361: Performance benchmarks http://bugs.jython.org/issue2361 opened by zyasoft #2362: Import * doesn't work on JDK9 http://bugs.jython.org/issue2362 opened by sfelts #2363: relative seeks works incorrectly after readline http://bugs.jython.org/issue2363 opened by amit Most recent 15 issues with no replies (15) ========================================== #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 #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 #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 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #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 #1612: array.array should use specialized bulk operations to initiali http://bugs.jython.org/issue1612 Top 10 most discussed issues (1) ================================ #2321: Need better API and docs for using PySystemState http://bugs.jython.org/issue2321 3 msgs Issues closed (1) ================= #2259: Relative, star imports ("from .module import *") broken with " http://bugs.jython.org/issue2259 closed by jeff.allen |
From: Jython t. <st...@bu...> - 2015-05-22 16:10:20
|
ACTIVITY SUMMARY (2015-05-15 - 2015-05-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 244 ( +0) closed 2133 ( +3) total 2377 ( +3) Open issues with patches: 26 Issues opened (3) ================= #2356: java.lang.IllegalArgumentException while startup jython on Win http://bugs.jython.org/issue2356 opened by liuxy_hes86 #2357: Infinite recursion with set subclass http://bugs.jython.org/issue2357 opened by jdemoor #2358: Jython fails to open readable file under /proc on Linux http://bugs.jython.org/issue2358 opened by dstromberg Most recent 15 issues with no replies (15) ========================================== #2358: Jython fails to open readable file under /proc on Linux http://bugs.jython.org/issue2358 #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 #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 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #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 #1612: array.array should use specialized bulk operations to initiali http://bugs.jython.org/issue1612 Top 10 most discussed issues (1) ================================ #1879: -m command line option broken for scripts inside a jar file http://bugs.jython.org/issue1879 5 msgs |
From: Rory O'D. <ror...@or...> - 2015-05-19 08:34:23
|
Hi Alan/Jim, Early Access build for JDK 9 b64 <https://jdk9.java.net/download/> is available on java.net, summary of changes are listed here <http://www.java.net/download/jdk9/changes/jdk9-b64.html> The JDK 9 schedule of record is available on the JDK 9 Project page: http://openjdk.java.net/projects/jdk9 Early Access build for JDK 8u60 b15 <http://jdk8.java.net/download.html> is available on java.net, summary of changes are listed here. <http://www.java.net/download/jdk8u60/changes/jdk8u60-b15.html> Note with 8077220 in 8u60 b12 , we are disabling the RC4 cipher suite by default. As we enter the later phases of development for JDK 8u60, please log any show stoppers as soon as possible. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland |
From: Darjus L. <da...@gm...> - 2015-05-19 03:43:47
|
Love the idea of putting it into github and making it more of a living thing. Darjus On Wed, May 13, 2015 at 3:45 AM Jim Baker <jim...@py...> wrote: > Some updates: > > - The repo for the Jython book has been moved to > https://github.com/jython/book. *Pull requests now gladly accepted*! > We should also move documentation issues from bugs.jython.org to the > issue tracker for the book itself in github. > - Sphinx build at http://jython.readthedocs.org/en/latest/ - Using > https://readthedocs.org/, I have set up a trigger on the above repo > such that Sphinx is now being generated against master. We will look at > what it will take to do this for specific PRs, but this likely less > important. > > > Next steps: > > - Not everything is building properly just yet - code samples are > still not linked, for example. But that's likely a trivial matter of > configuration with readthedocs.org, or possibly a slight moving around > of files. > - Point http://www.jython.org/jythonbook/en/1.0/, via CNAME, against > http://jython.readthedocs.org/en/latest/ > - Rearrange the book layout so it is easier to browse in source view > on GitHub. > > > - Jim > > On Tue, May 5, 2015 at 8:49 AM, Jim Baker <jim...@py...> wrote: > >> Julian, >> >> The Jython book should be updated. Given that the book is open source, >> under a CC-SA license, and that the source text is in reStructuredText, at >> https://kenai.com/projects/jythonbook (in Mercurial), it would be a >> simple matter of restarting. >> >> I suggest that we move the book development to a repo in >> https://github.com/jython, so we can take advantage of the tooling that >> is provided by GitHub. It's possible that we could even have CI that could >> generate new sections/chapters based on pull requests. As PRs are merged, >> we could automatically release updates, possibly also tagged eg to >> http://www.jython.org/jythonbook/en/2.x. Other languages could of course >> be hosted there as well. >> >> Setting this process up doesn't seem so much so work, which is good, >> because it's the content of the book itself that needs to be worked on! >> >> - Jim >> >> On Tue, May 5, 2015 at 1:47 AM, Julian Kennedy <jul...@gm...> >> wrote: >> >>> Hi guys >>> >>> First of all, Congrats on 2.7.0! Its been a while coming. :-) >>> >>> I notice that the jython book was last written/updated in 2010. Is the >>> content in there still relevant? And if not, are there any plans to update >>> it for the new release? >>> >>> Regards >>> >>> >>> ------------------------------------------------------------------------------ >>> One dashboard for servers and applications across Physical-Virtual-Cloud >>> Widest out-of-the-box monitoring support with 50+ applications >>> Performance metrics, stats and reports that give you Actionable Insights >>> Deep dive visibility with transaction tracing using APM Insight. >>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >>> >> >> >> -- >> - Jim >> >> jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} >> twitter.com/jimbaker >> github.com/jimbaker >> bitbucket.com/jimbaker >> > > > > -- > - Jim > > jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} > twitter.com/jimbaker > github.com/jimbaker > bitbucket.com/jimbaker > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jython t. <st...@bu...> - 2015-05-15 16:10:21
|
ACTIVITY SUMMARY (2015-05-08 - 2015-05-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 244 ( +4) closed 2130 ( +0) total 2374 ( +4) Open issues with patches: 26 Issues opened (5) ================= #1669: Interactive interpreter broken on Cygwin xterm http://bugs.jython.org/issue1669 reopened by zyasoft #2352: Support C_BUILTIN in _imp.load_module http://bugs.jython.org/issue2352 opened by jeff.allen #2353: jython.exe a 32-bit program on 64-bit Win8.1 even when install http://bugs.jython.org/issue2353 opened by GelattD #2354: marshal.py does not support serialization of code http://bugs.jython.org/issue2354 opened by fmartins #2355: Jython fails to import python modules from Lib when embedded i http://bugs.jython.org/issue2355 opened by otto_fajardo Most recent 15 issues with no replies (15) ========================================== #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 #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 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 #2245: Support non Unicode paths http://bugs.jython.org/issue2245 Most recent 15 issues waiting for review (15) ============================================= #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 #1612: array.array should use specialized bulk operations to initiali http://bugs.jython.org/issue1612 Top 10 most discussed issues (3) ================================ #2353: jython.exe a 32-bit program on 64-bit Win8.1 even when install http://bugs.jython.org/issue2353 4 msgs #2321: Need better API and docs for using PySystemState http://bugs.jython.org/issue2321 3 msgs #2355: Jython fails to import python modules from Lib when embedded i http://bugs.jython.org/issue2355 3 msgs Issues closed (1) ================= #2308: test___all__ fails at modjy http://bugs.jython.org/issue2308 closed by zyasoft |
From: Jim B. <jim...@py...> - 2015-05-12 17:44:41
|
Some updates: - The repo for the Jython book has been moved to https://github.com/jython/book. *Pull requests now gladly accepted*! We should also move documentation issues from bugs.jython.org to the issue tracker for the book itself in github. - Sphinx build at http://jython.readthedocs.org/en/latest/ - Using https://readthedocs.org/, I have set up a trigger on the above repo such that Sphinx is now being generated against master. We will look at what it will take to do this for specific PRs, but this likely less important. Next steps: - Not everything is building properly just yet - code samples are still not linked, for example. But that's likely a trivial matter of configuration with readthedocs.org, or possibly a slight moving around of files. - Point http://www.jython.org/jythonbook/en/1.0/, via CNAME, against http://jython.readthedocs.org/en/latest/ - Rearrange the book layout so it is easier to browse in source view on GitHub. - Jim On Tue, May 5, 2015 at 8:49 AM, Jim Baker <jim...@py...> wrote: > Julian, > > The Jython book should be updated. Given that the book is open source, > under a CC-SA license, and that the source text is in reStructuredText, at > https://kenai.com/projects/jythonbook (in Mercurial), it would be a > simple matter of restarting. > > I suggest that we move the book development to a repo in > https://github.com/jython, so we can take advantage of the tooling that > is provided by GitHub. It's possible that we could even have CI that could > generate new sections/chapters based on pull requests. As PRs are merged, > we could automatically release updates, possibly also tagged eg to > http://www.jython.org/jythonbook/en/2.x. Other languages could of course > be hosted there as well. > > Setting this process up doesn't seem so much so work, which is good, > because it's the content of the book itself that needs to be worked on! > > - Jim > > On Tue, May 5, 2015 at 1:47 AM, Julian Kennedy <jul...@gm...> > wrote: > >> Hi guys >> >> First of all, Congrats on 2.7.0! Its been a while coming. :-) >> >> I notice that the jython book was last written/updated in 2010. Is the >> content in there still relevant? And if not, are there any plans to update >> it for the new release? >> >> Regards >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> >> > > > -- > - Jim > > jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} > twitter.com/jimbaker > github.com/jimbaker > bitbucket.com/jimbaker > -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |
From: Jim B. <jim...@py...> - 2015-05-12 16:36:57
|
On Mon, May 11, 2015 at 9:11 PM, Stefan Richthofer <Ste...@gm... > wrote: > >>My feeling is that we should package dependencies like this, with > different license restrictions, in PyPI, eg we should support > >>pip install lijy > > Can this be done by the Jython installer? The JNI-based launcher should > really be the default (not only because of file-size, but also because of > this subprocess-thing). I would recommend to keep the python-launcher in > form of jython.py too for transparency. LiJy-launch is largely an exact > port of it, augmenting the launch-logic from the source of java.exe. So for > future developer-generations it will be easier to figure out what the > launcher is doing by looking at the python one. > I agree this would be the best, so long as we can avoid any license conflict. Maybe one possibility if we cannot avoid it is that we do the combination in the installer itself - the user can choose an option that immediately does `pip install lijy` I'm also in Vancouver next week for the OpenStack Summit, and I even on a panel ( https://openstacksummitmay2015vancouver.sched.org/event/fec286e14d4a1adb5f38a62f59196112), representing Jython, that's been organized by the PSF's lawyer ;) So I will try to get some good advice on what we can do from Van Lindberg. > >>One problem is that Windows, unlike Unix-like systems, has no built-in > support for replacing a file that is in-use > There is a working "default-solution" for this involving a temporary > bat-file. The method is not beautiful, but works and is frequently proposed > in forums etc. A collegue of mine used this technique successfully in one > of his projects, so I also know it from first hand. > Ah, makes sense. I think that would be a fine solution in this case. > > Then I have some questions about how jython.exe is created from > jython.py. I believe this was done by py2exe, wasn't it? > PyInstaller (https://github.com/pyinstaller/pyinstaller/wiki). However, there is a bug: http://bugs.jython.org/issue2343, which is that PyInstaller overwrites PYTHONPATH. Not so problematic for us, since we currently use JYTHONPATH, but could cause issues for code that passes through Jython. cxFreeze and py2exe are the two other options. > > 1) However, the py2exe-homepage (c.f. > http://www.py2exe.org/index.cgi/Tutorial) says one would have to bundle > MSVCR90.dll, which is not allowed for every VS distribution (e.g. it's not > allowed for VS express). How does Jython solve this? I didn't find an > MSVCR90.dll anywhere in Jython's dist-folder. > Was it statically linked? > So this is causing another issue in jython.exe, because we don't bundle this DLL, only the CPython 2.7 DLL. In certain cases, the C runtime DLLs are not available. It was mentioned on #jython with respect to running under Jenkins on Windows. I will try to find the link to the log text, but no bug was filed. > (For LiJy-launch I will try to build with VS 2010, so it can hopefully use > MSVCR100.dll, which is bundeled with Java7 and 8, or use win32 API for > basic stuff, so that kernel32.dll might be sufficient. If nothing works > out, I can still use mingw.) > > 2) How does this work regarding 32/64 bit? Is it actually possible to > control whether py2exe produces 32 or 64 bit executable? > Setting JAVA_HOME works, see http://bugs.jython.org/issue2353 > Is jython.exe a 32 bit executable that also runs on 64 bit systems? > Yes, I do that all of the time in my testing. It works because jython.exe calls java via a subprocess. > I am not confident that such a solution would be feasible for LiJy-launch, > since it must link to the architecture-dependent java.dll/.so. > So LiJy-launch will most likely come with multiple binaries (at least one > for 32 and 64 bit each). Can pip resolve this? > I believe this architectural issue should be resolvable with wheel support, indeed supporting different architectures for installations is one of the main design goals for wheels. - Jim |
From: Jim B. <jim...@py...> - 2015-05-09 19:52:24
|
FWIW, as of RC3, bin/jython.py -> bin/jython on platforms that support CPython 2.7. This can be readily relaxed and backported to CPython 2.5 or possibly CPython 2.4. My feeling is that we should package dependencies like this, with different license restrictions, in PyPI, eg we should support pip install lijy and they have a new launcher installed. There is a similar procedure for JRuby, https://rubygems.org/gems/jruby-launcher/versions/1.1.1-java; the process of compiling and linking could support systems we don't have wheels built for. Probably we should save the old launcher somewhere, so recovery could be done. One problem is that Windows, unlike Unix-like systems, has no built-in support for replacing a file that is in-use, other than using old utilities like inuse.exe (https://support.microsoft.com/en-us/kb/927229) - Jim On Sat, May 9, 2015 at 7:19 AM, Stefan Richthofer <Ste...@gm...> wrote: > Hi all, > > as kind of side-quest I have been working to write a JNI-based > Jython-launcher > with the mid-term goal to replace the current one that needs to bundle > CPython. > (I couldn't resist to make up some fancy development-name for the project.) > It turned out to be much harder than I thought, but finally, here is kind > of a > prototype (for now linux only). > I would appreciate some testing from the linux-users among you, before I > start > porting it to windows. > > Take a look at > https://github.com/Stewori/LiJy-launch (I wanna see some stars!) > Yes, the source code needs lots of clean-up; first do things right ;) > > I'd like to see this become the default-launcher in Jython 2.7.1, but > unfortunately > there might be license issues. It was infeasible to write this launcher > without > including source-code from Open JDK, which is released under GPLv2 with > classpath exception. However this would not be infective for Jython as > there is > the classpath exception and Jython would not link to the launcher anyway > (it's only > the other way round). > Only thing is that if Jython would distribute this launcher, it would have > to > clarify that the launcher is GPLv2 with classpath exception as opposed to > the rest > of Jython and include the according license text-file. > I suppose this should be okay, what do you think? > > Regards > > Stefan > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |
From: Stefan R. <Ste...@gm...> - 2015-05-09 13:19:57
|
Hi all, as kind of side-quest I have been working to write a JNI-based Jython-launcher with the mid-term goal to replace the current one that needs to bundle CPython. (I couldn't resist to make up some fancy development-name for the project.) It turned out to be much harder than I thought, but finally, here is kind of a prototype (for now linux only). I would appreciate some testing from the linux-users among you, before I start porting it to windows. Take a look at https://github.com/Stewori/LiJy-launch (I wanna see some stars!) Yes, the source code needs lots of clean-up; first do things right ;) I'd like to see this become the default-launcher in Jython 2.7.1, but unfortunately there might be license issues. It was infeasible to write this launcher without including source-code from Open JDK, which is released under GPLv2 with classpath exception. However this would not be infective for Jython as there is the classpath exception and Jython would not link to the launcher anyway (it's only the other way round). Only thing is that if Jython would distribute this launcher, it would have to clarify that the launcher is GPLv2 with classpath exception as opposed to the rest of Jython and include the according license text-file. I suppose this should be okay, what do you think? Regards Stefan |
From: Jeff A. <ja...@fa...> - 2015-05-09 08:42:17
|
You should expect some failures: see discussion in other posts on this list, and on the bug tracker, for what you should expect. I report fairly carefully what fails for me on Windows since I may be the only one to notice. These tests are the CPython regression tests for the most part. There are some additional tests for Jython, and some Jython-specific versions of the CPython tests, just as the standard library itself has Jython-specific versions. We try to keep special versions to a minimum, but they keep springing up. test___all__ tests the operation of the special attribute __all__, used to define what "from <m> import *" should actually import. This happens to be amongst the few handfuls of tests that Jython fails, albeit for a peripheral reason. (http://bugs.jython.org/issue2308) As Jim points out, -m test.regrtest -e is the thing to run. (Also for CPython, but the -e flag is only supported in the Jython-specific variant.) If you were toying with the idea of contributing to Jython (hint), you'll be typing that a lot. Jeff On 30/04/2015 02:44, Jim Baker wrote: > Run the tests like so: > > jython -m test.regrtest -e > > (-e means the expected tests for Jython, since we don't run all tests > from CPython. This option probably should be the default, as it is > with ant regrtest.) > > For the specific case of test_all, you will want to include on your > CLASSPATH a jar that (at least claims to) implement the servlet API. > You can use this one for that purpose: > https://github.com/jythontools/jython/blob/master/extlibs/servlet-api-2.5.jar > > Note that this doesn't apply to standalone since we don't bundle > tests. I suppose you can run them by setting JYTHONPATH to a Lib with > these tests, perhaps from a source checkout. > > - Jim > > On Wed, Apr 29, 2015 at 7:31 PM, Adam <ada...@gm... > <mailto:ada...@gm...>> wrote: > > Is there a standard way to run the test pack if you don't have the > jython source checked out? I tried running lib/test/test_all.py as > it seemed plausible but couldn't find explicit guidance in the > wiki or readme. Quite possible I missed something. > > Cheers > Adam > |
From: <fwi...@gm...> - 2015-05-09 00:41:46
|
On Fri, May 8, 2015 at 5:04 PM, Stefan Richthofer <Ste...@gm...> wrote: >> This would take much more than a conditional grammar, we'd have to >> somehow keep two runtimes around and be able to mix them. We'd need >> things like sometimes old style classes are permitted, sometimes not > > Hmmm I am honestly not 100% aware of all differences between Python 2 and 3 > to consider, so please apoligize if my thoughts are too naive. > Rather than two runtimes I imagine kind of one runtime that is the > "Least common multiple" of Python 2 and 3. (Jython already delivers a runtime > that is kind of "Least common multiple" of Python 2 and Java; extending > this to Python 3 sounds almost simple compared to what has already been achieved) > E.g. for the old- vs new-style classes concern: > Python 2.7 already _has_ this mix of old- and new style classes and deciding > whether to permit old ones would be trivial due to a different import-directive. > > However, if you say it can't be done (with reasonable effort), I trust you and > won't discuss further. I just wanted to make sure, the idea was considered. I do think it would be hard, but I wouldn't stop anyone from trying :) I think the hardest part would be keeping your head straight with simultaneous 2 and 3 behaviors - the trouble I see is that in too many respects 2 and 3 are too similar. I suspect the tiny differences would hurt the most. If you've ever tried switching back and forth between Python 2.5 and Python 2.7 - even those little differences can be *maddening* :) -Frank |
From: Stefan R. <Ste...@gm...> - 2015-05-09 00:04:19
|
> This would take much more than a conditional grammar, we'd have to > somehow keep two runtimes around and be able to mix them. We'd need > things like sometimes old style classes are permitted, sometimes not Hmmm I am honestly not 100% aware of all differences between Python 2 and 3 to consider, so please apoligize if my thoughts are too naive. Rather than two runtimes I imagine kind of one runtime that is the "Least common multiple" of Python 2 and 3. (Jython already delivers a runtime that is kind of "Least common multiple" of Python 2 and Java; extending this to Python 3 sounds almost simple compared to what has already been achieved) E.g. for the old- vs new-style classes concern: Python 2.7 already _has_ this mix of old- and new style classes and deciding whether to permit old ones would be trivial due to a different import-directive. However, if you say it can't be done (with reasonable effort), I trust you and won't discuss further. I just wanted to make sure, the idea was considered. Regards Stefan > Gesendet: Samstag, 09. Mai 2015 um 01:31 Uhr > Von: "fwi...@gm..." <fwi...@gm...> > An: "Stefan Richthofer" <Ste...@gm...> > Cc: "Jython Developers" <jyt...@li...> > Betreff: Re: Re: [Jython-dev] Jython 2.7.0 final released! > > On Fri, May 8, 2015 at 5:41 AM, Stefan Richthofer > <Ste...@gm...> wrote: > >>>grammar to keep 2.7 and 3.5 sort of parsing at the same time > > > > I had no idea this would be actually possible, but it sounds > > very interesting. Did you consider this as an actual feature > > for Jython3? > What might make sense someday if I have time would be conditional > parsing of either with the same grammar. Actually parsing at the same > time creates terrible things (and I am perpetrating terrible things > for now). > > For example, raise_stmt in Python2 is (from CPython's Grammar) looks like: > raise_stmt: 'raise' [test [',' test [',' test]]] > > Python3's is: > raise_stmt: 'raise' [test ['from' test]] > > What I am doing would translate to: > raise_stmt: 'raise' [test ['from'][',' test [',' test]]] > > Which would allow horrors like: > > raise Exception from None, foo, bar > > > Did you consider this as an actual feature > > for Jython3? Parsing 2.7 and 3.5 at the same time sounds weired, > > but what about something like a new import directive, let's say > > "import2" to import code that is known to be Python 2.7? > This would take much more than a conditional grammar, we'd have to > somehow keep two runtimes around and be able to mix them. We'd need > things like sometimes old style classes are permitted, sometimes not, > etc. That's definitely too hard (at least for me) and probably way too > ugly. Although it is the sort of crazy thing that can sometimes > interests Jim :) > > -Frank > |
From: <fwi...@gm...> - 2015-05-08 23:33:36
|
Oops the hybrid should have been: raise_stmt: 'raise' [test ['from' test][',' test [',' test]]] On Fri, May 8, 2015 at 4:31 PM, fwi...@gm... <fwi...@gm...> wrote: > On Fri, May 8, 2015 at 5:41 AM, Stefan Richthofer > <Ste...@gm...> wrote: >>>>grammar to keep 2.7 and 3.5 sort of parsing at the same time >> >> I had no idea this would be actually possible, but it sounds >> very interesting. Did you consider this as an actual feature >> for Jython3? > What might make sense someday if I have time would be conditional > parsing of either with the same grammar. Actually parsing at the same > time creates terrible things (and I am perpetrating terrible things > for now). > > For example, raise_stmt in Python2 is (from CPython's Grammar) looks like: > raise_stmt: 'raise' [test [',' test [',' test]]] > > Python3's is: > raise_stmt: 'raise' [test ['from' test]] > > What I am doing would translate to: > raise_stmt: 'raise' [test ['from'][',' test [',' test]]] > > Which would allow horrors like: > > raise Exception from None, foo, bar > >> Did you consider this as an actual feature >> for Jython3? Parsing 2.7 and 3.5 at the same time sounds weired, >> but what about something like a new import directive, let's say >> "import2" to import code that is known to be Python 2.7? > This would take much more than a conditional grammar, we'd have to > somehow keep two runtimes around and be able to mix them. We'd need > things like sometimes old style classes are permitted, sometimes not, > etc. That's definitely too hard (at least for me) and probably way too > ugly. Although it is the sort of crazy thing that can sometimes > interests Jim :) > > -Frank |
From: <fwi...@gm...> - 2015-05-08 23:31:59
|
On Fri, May 8, 2015 at 5:41 AM, Stefan Richthofer <Ste...@gm...> wrote: >>>grammar to keep 2.7 and 3.5 sort of parsing at the same time > > I had no idea this would be actually possible, but it sounds > very interesting. Did you consider this as an actual feature > for Jython3? What might make sense someday if I have time would be conditional parsing of either with the same grammar. Actually parsing at the same time creates terrible things (and I am perpetrating terrible things for now). For example, raise_stmt in Python2 is (from CPython's Grammar) looks like: raise_stmt: 'raise' [test [',' test [',' test]]] Python3's is: raise_stmt: 'raise' [test ['from' test]] What I am doing would translate to: raise_stmt: 'raise' [test ['from'][',' test [',' test]]] Which would allow horrors like: raise Exception from None, foo, bar > Did you consider this as an actual feature > for Jython3? Parsing 2.7 and 3.5 at the same time sounds weired, > but what about something like a new import directive, let's say > "import2" to import code that is known to be Python 2.7? This would take much more than a conditional grammar, we'd have to somehow keep two runtimes around and be able to mix them. We'd need things like sometimes old style classes are permitted, sometimes not, etc. That's definitely too hard (at least for me) and probably way too ugly. Although it is the sort of crazy thing that can sometimes interests Jim :) -Frank |
From: <fwi...@gm...> - 2015-05-08 16:28:07
|
On Fri, May 8, 2015 at 1:09 AM, Jeff Hardy <jd...@gm...> wrote: > Adding myself back into the conversation :) I'm sorry I should have asked if you wanted to stay on before removing you, very rude of me :) I figured we where to deep in the Jython weeds... > IronPython has been on GitHub for a while (almost 5 years), and it's > been brilliant. Concerns over lockin and etc. are completely > overblown; if we escaped from CodePlex, we can escape whatever lockin > GitHub tries to institute. I think the same way - since every checkout is the entire repository, there really isn't that much to worry about IMHO. > It *would* be nice to have a single stdlib repo, though. The current > ironpython3 repo stores it in a vendor branch, but I think this is one > case where having a submodule would work better. I just didn't bother > because I didn't have anyone to share it with. A couple of scripts and > hg-git should take care of keeping it up-to-date. Right now Jython keeps copies of the stdlib directly in our repo. I'd prefer something better, Ideally something coordinated with CPython. My plan for the first step in this direction is to get all of our modified versions checked into CPython's Lib. The point of this vs going for a split out Lib right away is to prove that "we're serious". I discussed this with the CPython folks almost 5 years ago now but never did anything about it. The advantage of this over our projects sharing a moded stdlib is that now as they make changes I/we wouldn't have to keep re-merging our mods (a time consuming pain). Anyway, once there is significant Jython (and maybe IronPython?) code in there I think we can make the case for CPython to consider breaking out the stdlib completely. There is also a faction of CPython devs that want to break out the stdlib for other reasons, so I bet this is a reasonably possible future. -Frank |
From: Jython t. <st...@bu...> - 2015-05-08 16:10:20
|
ACTIVITY SUMMARY (2015-05-01 - 2015-05-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 240 ( +0) closed 2130 ( +4) total 2370 ( +4) Open issues with patches: 26 Issues opened (3) ================= #2348: site module does not import if usernames contain non-ascii cha http://bugs.jython.org/issue2348 opened by fwierzbicki #2350: Installer errors on ensurepip http://bugs.jython.org/issue2350 opened by joshfriend #2351: Creating Lib.jar from the Lib directory http://bugs.jython.org/issue2351 opened by sergei175 Most recent 15 issues with no replies (15) ========================================== #2341: Invalid Unicode string literals cause console to keep outputti http://bugs.jython.org/issue2341 #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 #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 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2308: test___all__ fails at modjy http://bugs.jython.org/issue2308 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #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 #1612: array.array should use specialized bulk operations to initiali http://bugs.jython.org/issue1612 Top 10 most discussed issues (2) ================================ #2321: Need better API and docs for using PySystemState http://bugs.jython.org/issue2321 7 msgs #2350: Installer errors on ensurepip http://bugs.jython.org/issue2350 3 msgs Issues closed (3) ================= #1328: ctypes for jython http://bugs.jython.org/issue1328 closed by zyasoft #2158: Incorrect handling of relative, star imports ("from .module im http://bugs.jython.org/issue2158 closed by jeff.allen #2349: os.umask no longer exists? http://bugs.jython.org/issue2349 closed by zyasoft |
From: Stefan R. <Ste...@gm...> - 2015-05-08 12:41:17
|
>>grammar to keep 2.7 and 3.5 sort of parsing at the same time I had no idea this would be actually possible, but it sounds very interesting. Did you consider this as an actual feature for Jython3? Parsing 2.7 and 3.5 at the same time sounds weired, but what about something like a new import directive, let's say "import2" to import code that is known to be Python 2.7? > Gesendet: Donnerstag, 07. Mai 2015 um 19:06 Uhr > Von: "fwi...@gm..." <fwi...@gm...> > An: "Jim Baker" <jim...@py...> > Cc: "Jython Developers" <jyt...@li...> > Betreff: Re: [Jython-dev] Jython 2.7.0 final released! > > On Thu, May 7, 2015 at 8:35 AM, Jim Baker <jim...@py...> wrote: > > Suggestion: let's move https://hg.python.org/sandbox/jython3/ to > > https://github.com/jython/jython3 - we have enough commits going on here > > that it's best to move out of the sandbox and to an easier place to manage > > long term. > I'd love to move to git, but I don't think moving jython3 ahead alone > would make sense for me, at least for now. Right now I'm still doing > "hg pull ssl:hg...@hg.../jython whenever I see changes go into > the default branch. > > The wacky part is that I'm maintaining a 2.7 compatible version in > https://github.com/jython/jy3k. > > You should probably not look at the horrible things I'm doing in the > grammar to keep 2.7 and 3.5 sort of parsing at the same time :) > > -Frank > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jeff H. <jd...@gm...> - 2015-05-08 08:09:59
|
Adding myself back into the conversation :) IronPython has been on GitHub for a while (almost 5 years), and it's been brilliant. Concerns over lockin and etc. are completely overblown; if we escaped from CodePlex, we can escape whatever lockin GitHub tries to institute. It *would* be nice to have a single stdlib repo, though. The current ironpython3 repo stores it in a vendor branch, but I think this is one case where having a submodule would work better. I just didn't bother because I didn't have anyone to share it with. A couple of scripts and hg-git should take care of keeping it up-to-date. - Jeff On Fri, May 8, 2015 at 12:36 AM, Jim Baker <jim...@py...> wrote: > I don't think we care so much about the heatedness of that discussion :) > Practicality over purity, I suppose... > > On the one hand, I would like to use the new CPython tooling that is > currently being discussed. Unfortunately, as I learned at the PyCon sprints, > the plan of this tooling will itself not see initial review until late this > summer. > > On the other hand, we are not such a big project like CPython, we certainly > don't have the resources, and we would like to minimize our admin costs, > because that subtracts from actual dev time! Current dev is just too > painful, especially accepting PRs. > > Any number of critical Python projects, such as PyPA are now on GitHub. In > our case, we still own the repos, we can still mirror against > hg.python.org/jython, and moving the authoritative git repos is trivial > somewhere else, once we as a group agree. There is minimal lock-in, in other > words, other than our own inertia. > > - Jim > > > On Thu, May 7, 2015 at 4:56 PM, Jeff Allen <ja...@fa...> wrote: >> >> There was a long discussion on python-dev of moving CPython to GitHub >> (or BItBucket, or ...) which most of us probably saw. It was fairly >> heated, including objections concerning "FLOSS ethics" and lock-in. The >> outcome was to stick with PSF infrastructure for CPython, as we see, but >> there was a plan to move the documentation to a free (as in beer) service. >> >> I don't feel strongly, but wouldn't all the arguments apply equally to >> Jython? >> >> +1 for having all versions in the same official repo. >> >> Jeff Allen >> >> >> On 07/05/2015 18:13, fwi...@gm... wrote: >> > On Thu, May 7, 2015 at 10:08 AM, fwi...@gm... >> > <fwi...@gm...> wrote: >> >> On Thu, May 7, 2015 at 10:06 AM, fwi...@gm... >> >> <fwi...@gm...> wrote: >> >> >> >>> The wacky part is that I'm maintaining a 2.7 compatible version in >> >>> https://github.com/jython/jy3k. >> >> That was a typo/braino, don't get excited. It should have been: >> >> https://hg.python.org/sandbox/jy3k/ which is a very old branch I >> >> started years ago. >> > I guess we could make the sandbox branch a real branch in our main hg >> > repo. Would that help? >> > >> > P.S. I took Jeff off of the CC: and changed the subject since we are >> > way off of the announcement topic now :) >> > >> > -Frank >> > >> > >> > ------------------------------------------------------------------------------ >> > One dashboard for servers and applications across Physical-Virtual-Cloud >> > Widest out-of-the-box monitoring support with 50+ applications >> > Performance metrics, stats and reports that give you Actionable Insights >> > Deep dive visibility with transaction tracing using APM Insight. >> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> > _______________________________________________ >> > Jython-dev mailing list >> > Jyt...@li... >> > https://lists.sourceforge.net/lists/listinfo/jython-dev >> > >> >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > -- > - Jim > > jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} > twitter.com/jimbaker > github.com/jimbaker > bitbucket.com/jimbaker > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
From: Jim B. <jim...@py...> - 2015-05-07 23:37:13
|
I don't think we care so much about the heatedness of that discussion :) Practicality over purity, I suppose... On the one hand, I would like to use the new CPython tooling that is currently being discussed. Unfortunately, as I learned at the PyCon sprints, the plan of this tooling will itself not see initial review until late this summer. On the other hand, we are not such a big project like CPython, we certainly don't have the resources, and we would like to minimize our admin costs, because that subtracts from actual dev time! Current dev is just too painful, especially accepting PRs. Any number of critical Python projects, such as PyPA are now on GitHub. In our case, we still own the repos, we can still mirror against hg.python.org/jython, and moving the authoritative git repos is trivial somewhere else, once we as a group agree. There is minimal lock-in, in other words, other than our own inertia. - Jim On Thu, May 7, 2015 at 4:56 PM, Jeff Allen <ja...@fa...> wrote: > There was a long discussion on python-dev of moving CPython to GitHub > (or BItBucket, or ...) which most of us probably saw. It was fairly > heated, including objections concerning "FLOSS ethics" and lock-in. The > outcome was to stick with PSF infrastructure for CPython, as we see, but > there was a plan to move the documentation to a free (as in beer) service. > > I don't feel strongly, but wouldn't all the arguments apply equally to > Jython? > > +1 for having all versions in the same official repo. > > Jeff Allen > > > On 07/05/2015 18:13, fwi...@gm... wrote: > > On Thu, May 7, 2015 at 10:08 AM, fwi...@gm... > > <fwi...@gm...> wrote: > >> On Thu, May 7, 2015 at 10:06 AM, fwi...@gm... > >> <fwi...@gm...> wrote: > >> > >>> The wacky part is that I'm maintaining a 2.7 compatible version in > >>> https://github.com/jython/jy3k. > >> That was a typo/braino, don't get excited. It should have been: > >> https://hg.python.org/sandbox/jy3k/ which is a very old branch I > >> started years ago. > > I guess we could make the sandbox branch a real branch in our main hg > > repo. Would that help? > > > > P.S. I took Jeff off of the CC: and changed the subject since we are > > way off of the announcement topic now :) > > > > -Frank > > > > > ------------------------------------------------------------------------------ > > One dashboard for servers and applications across Physical-Virtual-Cloud > > Widest out-of-the-box monitoring support with 50+ applications > > Performance metrics, stats and reports that give you Actionable Insights > > Deep dive visibility with transaction tracing using APM Insight. > > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > > _______________________________________________ > > Jython-dev mailing list > > Jyt...@li... > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |
From: Jeff A. <ja...@fa...> - 2015-05-07 22:56:20
|
There was a long discussion on python-dev of moving CPython to GitHub (or BItBucket, or ...) which most of us probably saw. It was fairly heated, including objections concerning "FLOSS ethics" and lock-in. The outcome was to stick with PSF infrastructure for CPython, as we see, but there was a plan to move the documentation to a free (as in beer) service. I don't feel strongly, but wouldn't all the arguments apply equally to Jython? +1 for having all versions in the same official repo. Jeff Allen On 07/05/2015 18:13, fwi...@gm... wrote: > On Thu, May 7, 2015 at 10:08 AM, fwi...@gm... > <fwi...@gm...> wrote: >> On Thu, May 7, 2015 at 10:06 AM, fwi...@gm... >> <fwi...@gm...> wrote: >> >>> The wacky part is that I'm maintaining a 2.7 compatible version in >>> https://github.com/jython/jy3k. >> That was a typo/braino, don't get excited. It should have been: >> https://hg.python.org/sandbox/jy3k/ which is a very old branch I >> started years ago. > I guess we could make the sandbox branch a real branch in our main hg > repo. Would that help? > > P.S. I took Jeff off of the CC: and changed the subject since we are > way off of the announcement topic now :) > > -Frank > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |