Menu
▾
▴
jython-dev
|
From: <fwi...@gm...> - 2017-05-24 00:35:51
|
On Tue, May 23, 2017 at 5:29 PM, fwi...@gm... <fwi...@gm...> wrote: > On Sat, May 20, 2017 at 5:00 PM, Stefan Richthofer > <Ste...@gm...> wrote: >> I'd like to have http://bugs.jython.org/issue2536 "fixed" by removing that >> infinite recursion test; maybe we could even close this annoying issue then. >> A new Jython release should have reliable test suite. However I don't know >> the best way to remove or blacklist a certain test. > I don't think I saw anyone answer this (but the thread is long so I > may have missed it) but if you look in regrtest.py you'll see a list > starting around line 880, with one section called 'java'. That's a > list of tests that are deliberately skipped. That list hasn't been > looked at in a long time, and I bet there are tests in there that > actually shouldn't get skipped anymore... but that's a whole different > can of worms :) Or if you are talking about a single test function and not a whole test file something like this decorating the particular test will work: @unittest.skipIf(test_support.is_jython, "Not a valid test for Jython") |
|
From: Jeff A. <ja...@fa...> - 2017-05-24 07:56:33
|
Sorry, I should have taken Stefan's hint. Yes, if we need to exclude a whole test, then there are lists in regrtest.py as Frank says. This is quite a crude tool, perhaps best suited to tests whose entire purpose is irrelevant to Jython or that interfere with subsequent tests. It is better to skip individual tests as Frank also indicates. Some tests really are not appropriate to Jython (mostly involving garbage collection) because Jython is different and we're happy with it that way. In other cases, it's a shortcoming of some kind and we should say so in the skip message. Ideally, the skip message or a comment in regrtest.py where the exclusion happens, according to the approach taken, links to an open issue. That way, we haven't just silenced the alarm. Jeff Jeff Allen On 24/05/2017 01:35, fwi...@gm... wrote: > On Tue, May 23, 2017 at 5:29 PM, fwi...@gm... > <fwi...@gm...> wrote: >> On Sat, May 20, 2017 at 5:00 PM, Stefan Richthofer >> <Ste...@gm...> wrote: >>> I'd like to have http://bugs.jython.org/issue2536 "fixed" by removing that >>> infinite recursion test; maybe we could even close this annoying issue then. >>> A new Jython release should have reliable test suite. However I don't know >>> the best way to remove or blacklist a certain test. >> I don't think I saw anyone answer this (but the thread is long so I >> may have missed it) but if you look in regrtest.py you'll see a list >> starting around line 880, with one section called 'java'. That's a >> list of tests that are deliberately skipped. That list hasn't been >> looked at in a long time, and I bet there are tests in there that >> actually shouldn't get skipped anymore... but that's a whole different >> can of worms :) > Or if you are talking about a single test function and not a whole > test file something like this decorating the particular test will > work: > > @unittest.skipIf(test_support.is_jython, "Not a valid test for Jython") > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Stefan R. <Ste...@gm...> - 2017-05-24 16:27:29
|
Hey Jeff, Frank thanks for coming back to this. However, I already helped myself to some extend. I wouldn't have asked if it was as simple as adding @skip. That's an option, but maybe not the "right" way (I should have been more specific). Specifically, the following tests should be excluded from test suite or moved to the very end (how to do that somewhat the "right" way?), because they potentially mess up guava internals such that later deadlocks can occur: test_json: Features its own test-suite, so not sure how well it is possible to exclude certain test files using regrtest.py, i.e. Lib/json/tests/test_recursion.py. Relevant tests to exclude from that file are: test_highly_nested_objects_decoding test_highly_nested_objects_encoding test_endless_recursion test_isinstance: test_subclass_recursion_limit test_isinstance_recursion_limit So, I'll just add @skipIf... to these, given that they are customized for Jython already, being in Lib. If you'd say we better exclude test_json and test_isinstance via regrtest.py or move them to the end, tell me... Maybe we'd better continue with this on bugtracker/#2536, if at all. Best -Stefan > Gesendet: Mittwoch, 24. Mai 2017 um 09:55 Uhr > Von: "Jeff Allen" <ja...@fa...> > An: jyt...@li... > Betreff: Re: [Jython-dev] Unicode user and file names (and v2.7.1) > > Sorry, I should have taken Stefan's hint. > > Yes, if we need to exclude a whole test, then there are lists in > regrtest.py as Frank says. This is quite a crude tool, perhaps best > suited to tests whose entire purpose is irrelevant to Jython or that > interfere with subsequent tests. > > It is better to skip individual tests as Frank also indicates. Some > tests really are not appropriate to Jython (mostly involving garbage > collection) because Jython is different and we're happy with it that > way. In other cases, it's a shortcoming of some kind and we should say > so in the skip message. > > Ideally, the skip message or a comment in regrtest.py where the > exclusion happens, according to the approach taken, links to an open > issue. That way, we haven't just silenced the alarm. > > Jeff > > Jeff Allen > > On 24/05/2017 01:35, fwi...@gm... wrote: > > On Tue, May 23, 2017 at 5:29 PM, fwi...@gm... > > <fwi...@gm...> wrote: > >> On Sat, May 20, 2017 at 5:00 PM, Stefan Richthofer > >> <Ste...@gm...> wrote: > >>> I'd like to have http://bugs.jython.org/issue2536 "fixed" by removing that > >>> infinite recursion test; maybe we could even close this annoying issue then. > >>> A new Jython release should have reliable test suite. However I don't know > >>> the best way to remove or blacklist a certain test. > >> I don't think I saw anyone answer this (but the thread is long so I > >> may have missed it) but if you look in regrtest.py you'll see a list > >> starting around line 880, with one section called 'java'. That's a > >> list of tests that are deliberately skipped. That list hasn't been > >> looked at in a long time, and I bet there are tests in there that > >> actually shouldn't get skipped anymore... but that's a whole different > >> can of worms :) > > Or if you are talking about a single test function and not a whole > > test file something like this decorating the particular test will > > work: > > > > @unittest.skipIf(test_support.is_jython, "Not a valid test for Jython") > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Jython-dev mailing list > > Jyt...@li... > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Jeff A. <ja...@fa...> - 2017-05-24 20:30:28
|
If it messes up later tests then, until it can be fixed, I think the apparatus we have for excluding it applies. However, an extra test that would fail in that case might be a good addition. BTW when diagnosing that kind of thing, I've found it useful that regrtest takes a list of tests on the command line, or in a file, and runs them in the order given (and as many times as given). +1 for adding fine-grain skips as you intend, mentioning the most appropriate issue. Jeff Allen On 24/05/2017 17:27, Stefan Richthofer wrote: > Hey Jeff, Frank > > thanks for coming back to this. However, I already helped myself to some extend. > I wouldn't have asked if it was as simple as adding @skip. That's an option, but maybe not the "right" way (I should have been more specific). > > Specifically, the following tests should be excluded from test suite or moved to the very end (how to do that somewhat the "right" way?), because they potentially mess up guava internals such that later deadlocks can occur: > > test_json: Features its own test-suite, so not sure how well it is possible to exclude certain test files using regrtest.py, i.e. Lib/json/tests/test_recursion.py. Relevant tests to exclude from that file are: > > test_highly_nested_objects_decoding > test_highly_nested_objects_encoding > test_endless_recursion > > > test_isinstance: > test_subclass_recursion_limit > test_isinstance_recursion_limit > > So, I'll just add @skipIf... to these, given that they are customized for Jython already, being in Lib. If you'd say we better exclude test_json and test_isinstance via regrtest.py or move them to the end, tell me... > Maybe we'd better continue with this on bugtracker/#2536, if at all. > > Best > > -Stefan > > >> Gesendet: Mittwoch, 24. Mai 2017 um 09:55 Uhr >> Von: "Jeff Allen" <ja...@fa...> >> An: jyt...@li... >> Betreff: Re: [Jython-dev] Unicode user and file names (and v2.7.1) >> >> Sorry, I should have taken Stefan's hint. >> >> Yes, if we need to exclude a whole test, then there are lists in >> regrtest.py as Frank says. This is quite a crude tool, perhaps best >> suited to tests whose entire purpose is irrelevant to Jython or that >> interfere with subsequent tests. >> >> It is better to skip individual tests as Frank also indicates. Some >> tests really are not appropriate to Jython (mostly involving garbage >> collection) because Jython is different and we're happy with it that >> way. In other cases, it's a shortcoming of some kind and we should say >> so in the skip message. >> >> Ideally, the skip message or a comment in regrtest.py where the >> exclusion happens, according to the approach taken, links to an open >> issue. That way, we haven't just silenced the alarm. >> >> Jeff >> >> Jeff Allen >> >> On 24/05/2017 01:35, fwi...@gm... wrote: >>> On Tue, May 23, 2017 at 5:29 PM, fwi...@gm... >>> <fwi...@gm...> wrote: >>>> On Sat, May 20, 2017 at 5:00 PM, Stefan Richthofer >>>> <Ste...@gm...> wrote: >>>>> I'd like to have http://bugs.jython.org/issue2536 "fixed" by removing that >>>>> infinite recursion test; maybe we could even close this annoying issue then. >>>>> A new Jython release should have reliable test suite. However I don't know >>>>> the best way to remove or blacklist a certain test. >>>> I don't think I saw anyone answer this (but the thread is long so I >>>> may have missed it) but if you look in regrtest.py you'll see a list >>>> starting around line 880, with one section called 'java'. That's a >>>> list of tests that are deliberately skipped. That list hasn't been >>>> looked at in a long time, and I bet there are tests in there that >>>> actually shouldn't get skipped anymore... but that's a whole different >>>> can of worms :) >>> Or if you are talking about a single test function and not a whole >>> test file something like this decorating the particular test will >>> work: >>> >>> @unittest.skipIf(test_support.is_jython, "Not a valid test for Jython") >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> |
|
From: Stefan R. <Ste...@gm...> - 2017-05-24 17:27:06
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div>Did someone test this on OSX? (reminder: <a href="https://github.com/Stewori/jython" target="_blank">https://github.com/Stewori/jython</a>)</div> <div>Or on Java 7?</div> <div>I just tested on Java 7 and the only test I observe to fail unexpectedly is test_random:</div> <div> </div> <div>test_random crashed -- <type 'exceptions.IOError'>: [Errno 13] Permission denied: '/data/workspace/linux/Jython_extlib/jython/dist/testreports/TEST-test.test_random.WichmannHill_TestBasicOps.xml'</div> <div> </div> <div>The test passes when run individually.</div> <div> </div> <div>However that is on my old laptop running Linux Mint Debian/LMDE2. It seems to be</div> <div>some io error due to access rights and also occurs when running with Java8 on that</div> <div>machine. Note that it passes with Java 8 on my current system. Unless this is due to</div> <div>Java 8_111 vs Java 8_131, I guess it's system dependent. Strange though:</div> <div>worked well before extlib update.</div> <div> </div> <div>Still I'd suggest to get this stuff in for RC-phase, given that the test passes individually.</div> <div>I'd merge this stuff as soon as someone reports OSX results.</div> <div> </div> <div>-Stefan</div> <div> </div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Dienstag, 23. Mai 2017 um 23:57 Uhr<br/> <b>Von:</b> "Stefan Richthofer" <Ste...@gm...><br/> <b>An:</b> "Jim Baker" <jim...@py...><br/> <b>Cc:</b> "Jython Developers" <jyt...@li...><br/> <b>Betreff:</b> Re: [Jython-dev] Updating extlibs</div> <div name="quoted-content"> <div style="font-family: Verdana;font-size: 12.0px;"> <div> <div>Just noticed guava > 20.0 requires Java 8.</div> <div>Strange thing: When building and running Jython on Java 8 with guava 22.0 all regrtests pass fine, but jar-standalone build is bad. Seems like our ant task fails to copy com.google -> org.python.google. Note that I double and triple checked I adjusted build.xml correctly. Is this related to jarjar? Is it maybe not compatible with Java8 jar-files? This might become a problem at some point.</div> <div>Studying guava 22.0 release notes more properly showed that one shall use guava-22.0-android.jar to target Java 7 also on non-Android platforms. With guava-22.0-android.jar, building Jython jar-standalone works well indeed. regrtests also seem to pass then.</div> <div>Ideas?</div> <div>I'll update the linked repo from last email with guava-22.0-android.jar...</div> <div> <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Montag, 22. Mai 2017 um 17:22 Uhr<br/> <b>Von:</b> "Jim Baker" <jim...@py...><br/> <b>An:</b> "Stefan Richthofer" <Ste...@gm...><br/> <b>Cc:</b> "Jython Developers" <jyt...@li...><br/> <b>Betreff:</b> Re: [Jython-dev] Updating extlibs</div> <div> <div>These changes look good to me. I will test out your patch, but all of this is in line with similar updates we have made in the past, usually around this time in the dev cycle. <div> </div> <div>I'm glad that moving to Gradle will make this re-pinning to upstream dependencies much easier going forward!</div> </div> <div class="gmail_extra"> <div class="gmail_quote">On Mon, May 22, 2017 at 8:46 AM, Stefan Richthofer <span><<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>></span> wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">I uploaded the mentioned updates to<br/> <a href="https://github.com/Stewori/jython" target="_blank">https://github.com/Stewori/jython</a>.<br/> See detailed changes at<br/> <a href="https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e9499afc6d02267648ac36" target="_blank">https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e9499afc6d02267648ac36</a><br/> <br/> This might not yet work smoothly with Java 7, I will check and adjust that tomorrow.<br/> Some packages were built from source using Java 8 and I'm not sure whether the gradle<br/> scripts always configured Java 7 source compatibility properly.<br/> However if some people could test it, especially on OSX, would be nice.<br/> <br/> Best<br/> <br/> Stefan<br/> <br/> <br/> > Gesendet: Montag, 22. Mai 2017 um 04:07 Uhr<br/> > Von: "Stefan Richthofer" <<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>><br/> > An: "Jython Developers" <<a href="mailto:jyt...@li..." onclick="parent.window.location.href='jyt...@li...'; return false;" target="_blank">jyt...@li...</a>><br/> > Betreff: Updating extlibs <div class="HOEnZb"> <div class="h5">><br/> > Hey all,<br/> > I spent some effort to explore feasibility of updating extlibs, especially minor versions (but sometimes even major version, e.g. guava and icu4j).<br/> > My results so far, tested with regrtest on Linux and Windows 10 using Java8 ("okay" means I did not observe additional regrtest failures):<br/> ><br/> > ASM 5.0.4 -> 5.2 okay<br/> > bouncycastle:<br/> > bcpkix-jdk15on-1.54 -> 1.57 okay<br/> > bcprov-jdk15on-1.54 -> 1.57 okay<br/> ><br/> > commons-compress-1.12 -> 1.14 okay<br/> > guava-20.0 -> 22.0rc1 okay<br/> > icu4j-58.1 -> 59_1 okay<br/> > Netty 4.1.6 -> 4.1.11 okay<br/> > java-sizeof-0.0.5 -- still current<br/> > jffi-1.2.13 -> 1.2.15 okay<br/> > jnr-ffi-2.1.0 -> 2.1.5 okay<br/> > jnr-netdb-1.1.6 -- still current<br/> > jnr-posix-3.0.31 -> 3.0.41 okay<br/> > jnr-constants-0.9.5 -> 0.9.9 okay<br/> > New platforms: jffi-aarch64-Linux.jar, jffi-ppc64le-Linux.jar, can be added...?<br/> > Updated various other changed platform specific jars to jffi-1.2.15 (okay as far as tested)<br/> > xercesImpl-2.11.0 -- still current<br/> > jline-2.14.2 -> 2.14.3 okay (didn't try jline-3 this time)<br/> > jarjar-1.4 -- still current<br/> > mysql-connector-java-5.1.6 -> 5.1.42 okay<br/> > postgresql-8.3-603.jdbc4 -> 42.1.1-jre7 okay<br/> ><br/> > ----------These failed, so leaving them as it is:<br/> > Antlr 3.1.3 -> 3.5.2 fails<br/> > junit-4.10 -> 4.12 or 4.11 class file for org.hamcrest.Matcher not found<br/> > (staying with 4.10 for now to avoid new dependency on hamcrest-matcher)<br/> > javax.servlet-api-2.5 -> 3.1.0 fails<br/> > mockrunner (better don't touch; whole structure changed)<br/> > cpptasks (better don't touch)<br/> ><br/> > - will be able to test with Java 7 on Tuesday, because I left my old laptop in the office.<br/> > - will upload a fork containing these updates. Would be good if someone else could also test, especially on OSX.<br/> > Maybe some stuff was not covered by regrtests. However the chance that updates solve issues and that they create issues are probably somewhat equal and I'd prefer to focus on fixing issues with current versions rather than older ones.<br/> > So I'm strongly for getting this in if regrtests go through on Java 7 and OSX. 2.7.1RC-phase will be a good opportunity to confirm workability of these updates. Any concerns?<br/> ><br/> > -Stefan<br/> <br/> ------------------------------------------------------------------------------<br/> Check out the vibrant tech community on one of the world's most<br/> engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a><br/> _______________________________________________<br/> Jython-dev mailing list<br/> <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a><br/> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></div> </div> </blockquote> </div> </div> </div> </div> </div> </div> </div> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot_______________________________________________" target="_blank">http://sdm.link/slashdot_______________________________________________</a> Jython-dev mailing list Jyt...@li... <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></div> </div> </div> </div></div></body></html> |
|
From: Jim B. <jim...@py...> - 2017-05-26 18:17:08
|
Stefan, You can apply these updates to extlibs, based on my testing on OSX. More below. I was able to run the following on both Java 7 and Java 8 on OSX: pip/setuptools installation smoke test fully succeeds, using the manual test described in http://bugs.jython.org/issue2570 (we should look at automating, at least with a simple bash script) regrtest. I did observe flakiness in test_socket_jy, which may require more rounds of waiting, but it does not appear to happen unless it's run in the context of other tests, so full runs of the regrtest. (And IIRC, appeared in the past before extlib update. It has been a well-known flaky test.) For Java 7, test_codecencodings_tw continues to not completely pass, almost certainly due to changes in underlying Java support (a bug fix that was not applied to Java 7). It has nothing to do with these extlib updates. Note that test_socket is shaking out some problems, likely due to the Netty update further refining the exceptions it throws. It's worth noting that error states are not documented very well for either C sockets or Netty's rather different support, so we have to explore the implemented behavior. So one example I saw that should be fixed at some point (possibly not for 2.7.1, there will always be more bugs, and certainly higher priority ones IMHO at this time): [exec] Unhandled exception in thread started by <bound method BasicTCPTest.clientRun of testShutdown (test.test_socket.BasicTCPTest)> [exec] Traceback (most recent call last): [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/test/test_socket.py", line 186, in clientRun [exec] self.clientSetUp() [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/test/test_socket.py", line 246, in clientSetUp [exec] self.cli.connect((self.HOST, self.PORT)) [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 1441, in meth [exec] return getattr(self._sock,name)(*args) [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 935, in connect [exec] self._connect(addr) [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 911, in _connect [exec] self._handle_channel_future(self.connect_future, "connect") [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 384, in handle_exception [exec] raise _map_exception(jlx) [exec] _socket.error: [Errno -1] Unmapped exception: io.netty.channel.AbstractChannel$AnnotatedSocketException: Invalid argument: localhost/127.0.0.1:50100 I was unable to see this error thrown again, but we may have enough to still fix in the exception mapping code. - Jim On Wed, May 24, 2017 at 1:26 PM, Stefan Richthofer <Ste...@gm... > wrote: > Did someone test this on OSX? (reminder: https://github.com/Stewori/jython > ) > Or on Java 7? > I just tested on Java 7 and the only test I observe to fail unexpectedly > is test_random: > > test_random crashed -- <type 'exceptions.IOError'>: [Errno 13] Permission > denied: '/data/workspace/linux/Jython_extlib/jython/dist/ > testreports/TEST-test.test_random.WichmannHill_TestBasicOps.xml' > > The test passes when run individually. > > However that is on my old laptop running Linux Mint Debian/LMDE2. It seems > to be > some io error due to access rights and also occurs when running with Java8 > on that > machine. Note that it passes with Java 8 on my current system. Unless this > is due to > Java 8_111 vs Java 8_131, I guess it's system dependent. Strange though: > worked well before extlib update. > > Still I'd suggest to get this stuff in for RC-phase, given that the test > passes individually. > I'd merge this stuff as soon as someone reports OSX results. > > -Stefan > > > *Gesendet:* Dienstag, 23. Mai 2017 um 23:57 Uhr > *Von:* "Stefan Richthofer" <Ste...@gm...> > *An:* "Jim Baker" <jim...@py...> > > *Cc:* "Jython Developers" <jyt...@li...> > *Betreff:* Re: [Jython-dev] Updating extlibs > Just noticed guava > 20.0 requires Java 8. > Strange thing: When building and running Jython on Java 8 with guava 22.0 > all regrtests pass fine, but jar-standalone build is bad. Seems like our > ant task fails to copy com.google -> org.python.google. Note that I double > and triple checked I adjusted build.xml correctly. Is this related to > jarjar? Is it maybe not compatible with Java8 jar-files? This might become > a problem at some point. > Studying guava 22.0 release notes more properly showed that one shall use > guava-22.0-android.jar to target Java 7 also on non-Android platforms. With > guava-22.0-android.jar, building Jython jar-standalone works well indeed. > regrtests also seem to pass then. > Ideas? > I'll update the linked repo from last email with guava-22.0-android.jar... > > *Gesendet:* Montag, 22. Mai 2017 um 17:22 Uhr > *Von:* "Jim Baker" <jim...@py...> > *An:* "Stefan Richthofer" <Ste...@gm...> > *Cc:* "Jython Developers" <jyt...@li...> > *Betreff:* Re: [Jython-dev] Updating extlibs > These changes look good to me. I will test out your patch, but all of this > is in line with similar updates we have made in the past, usually around > this time in the dev cycle. > > I'm glad that moving to Gradle will make this re-pinning to upstream > dependencies much easier going forward! > > On Mon, May 22, 2017 at 8:46 AM, Stefan Richthofer < > Ste...@gm...> wrote: >> >> I uploaded the mentioned updates to >> https://github.com/Stewori/jython. >> See detailed changes at >> https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e9499afc6d02 >> 267648ac36 >> >> This might not yet work smoothly with Java 7, I will check and adjust >> that tomorrow. >> Some packages were built from source using Java 8 and I'm not sure >> whether the gradle >> scripts always configured Java 7 source compatibility properly. >> However if some people could test it, especially on OSX, would be nice. >> >> Best >> >> Stefan >> >> >> > Gesendet: Montag, 22. Mai 2017 um 04:07 Uhr >> > Von: "Stefan Richthofer" <Ste...@gm...> >> > An: "Jython Developers" <jyt...@li...> >> > Betreff: Updating extlibs >> > >> > Hey all, >> > I spent some effort to explore feasibility of updating extlibs, >> especially minor versions (but sometimes even major version, e.g. guava and >> icu4j). >> > My results so far, tested with regrtest on Linux and Windows 10 using >> Java8 ("okay" means I did not observe additional regrtest failures): >> > >> > ASM 5.0.4 -> 5.2 okay >> > bouncycastle: >> > bcpkix-jdk15on-1.54 -> 1.57 okay >> > bcprov-jdk15on-1.54 -> 1.57 okay >> > >> > commons-compress-1.12 -> 1.14 okay >> > guava-20.0 -> 22.0rc1 okay >> > icu4j-58.1 -> 59_1 okay >> > Netty 4.1.6 -> 4.1.11 okay >> > java-sizeof-0.0.5 -- still current >> > jffi-1.2.13 -> 1.2.15 okay >> > jnr-ffi-2.1.0 -> 2.1.5 okay >> > jnr-netdb-1.1.6 -- still current >> > jnr-posix-3.0.31 -> 3.0.41 okay >> > jnr-constants-0.9.5 -> 0.9.9 okay >> > New platforms: jffi-aarch64-Linux.jar, jffi-ppc64le-Linux.jar, can be >> added...? >> > Updated various other changed platform specific jars to jffi-1.2.15 >> (okay as far as tested) >> > xercesImpl-2.11.0 -- still current >> > jline-2.14.2 -> 2.14.3 okay (didn't try jline-3 this >> time) >> > jarjar-1.4 -- still current >> > mysql-connector-java-5.1.6 -> 5.1.42 okay >> > postgresql-8.3-603.jdbc4 -> 42.1.1-jre7 okay >> > >> > ----------These failed, so leaving them as it is: >> > Antlr 3.1.3 -> 3.5.2 fails >> > junit-4.10 -> 4.12 or 4.11 class file for >> org.hamcrest.Matcher not found >> > (staying with 4.10 for now to avoid new dependency on hamcrest-matcher) >> > javax.servlet-api-2.5 -> 3.1.0 fails >> > mockrunner (better don't touch; whole structure changed) >> > cpptasks (better don't touch) >> > >> > - will be able to test with Java 7 on Tuesday, because I left my old >> laptop in the office. >> > - will upload a fork containing these updates. Would be good if someone >> else could also test, especially on OSX. >> > Maybe some stuff was not covered by regrtests. However the chance that >> updates solve issues and that they create issues are probably somewhat >> equal and I'd prefer to focus on fixing issues with current versions rather >> than older ones. >> > So I'm strongly for getting this in if regrtests go through on Java 7 >> and OSX. 2.7.1RC-phase will be a good opportunity to confirm workability of >> these updates. Any concerns? >> > >> > -Stefan >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most engaging > tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ Jython-dev mailing list > Jyt...@li... https://lists.sourceforge.net/ > lists/listinfo/jython-dev > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > |
|
From: Stefan R. <Ste...@gm...> - 2017-05-26 23:19:15
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div>> You can apply these updates to extlibs</div> <div>Done as of <a href="https://hg.python.org/jython/rev/f6b3ddbc1df8" target="_blank">https://hg.python.org/jython/rev/f6b3ddbc1df8</a>.</div> <div> </div> <div>From my point of view we can launch Jython 2.7.1-RC2 now.</div> <div> </div> <div>- no open PRs on github left</div> <div>- no release blockers left apparently <strike>except #2487</strike></div> <div>- all updates done as far as possible (python std-lib will be next challenge on this front)</div> <div> </div> <div>So, I'd suggest everybody pushes last-minute work and Frank hits the release-button... :-)</div> <div>What do you think?</div> <div> </div> <div> </div> <div>Cheers!</div> <div> </div> <div>-Stefan</div> <div> </div> <div> <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Freitag, 26. Mai 2017 um 20:16 Uhr<br/> <b>Von:</b> "Jim Baker" <jim...@py...><br/> <b>An:</b> "Stefan Richthofer" <Ste...@gm...><br/> <b>Cc:</b> "Jython Developers" <jyt...@li...><br/> <b>Betreff:</b> Re: [Jython-dev] Updating extlibs</div> <div> <div>Stefan, <div> </div> <div>You can apply these updates to extlibs, based on my testing on OSX. More below.</div> <div> </div> <div> </div> <div>I was able to run the following on both Java 7 and Java 8 on OSX:</div> <div> </div> <div>pip/setuptools installation smoke test fully succeeds, using the manual test described in <a href="http://bugs.jython.org/issue2570" target="_blank">http://bugs.jython.org/issue2570</a> (we should look at automating, at least with a simple bash script)</div> <div> </div> <div>regrtest. I did observe flakiness in test_socket_jy, which may require more rounds of waiting, but it does not appear to happen unless it's run in the context of other tests, so full runs of the regrtest. (And IIRC, appeared in the past before extlib update. It has been a well-known flaky test.) For Java 7, test_codecencodings_tw continues to not completely pass, almost certainly due to changes in underlying Java support (a bug fix that was not applied to Java 7). It has nothing to do with these extlib updates.</div> <div> </div> <div>Note that test_socket is shaking out some problems, likely due to the Netty update further refining the exceptions it throws. It's worth noting that error states are not documented very well for either C sockets or Netty's rather different support, so we have to explore the implemented behavior. So one example I saw that should be fixed at some point (possibly not for 2.7.1, there will always be more bugs, and certainly higher priority ones IMHO at this time):</div> <div> </div> <div> <div> [exec] Unhandled exception in thread started by <bound method BasicTCPTest.clientRun of testShutdown (test.test_socket.BasicTCPTest)></div> <div> [exec] Traceback (most recent call last):</div> <div> [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/test/test_socket.py", line 186, in clientRun</div> <div> [exec] self.clientSetUp()</div> <div> [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/test/test_socket.py", line 246, in clientSetUp</div> <div> [exec] self.cli.connect((self.HOST, self.PORT))</div> <div> [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 1441, in meth</div> <div> [exec] return getattr(self._sock,name)(*args)</div> <div> [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 935, in connect</div> <div> [exec] self._connect(addr)</div> <div> [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 911, in _connect</div> <div> [exec] self._handle_channel_future(self.connect_future, "connect")</div> <div> [exec] File "/Users/jbaker/jythondev/jython-extlibs/dist/Lib/_socket.py", line 384, in handle_exception</div> <div> [exec] raise _map_exception(jlx)</div> <div> [exec] _socket.error: [Errno -1] Unmapped exception: io.netty.channel.AbstractChannel$AnnotatedSocketException: Invalid argument: localhost/<a href="http://127.0.0.1:50100" target="_blank">127.0.0.1:50100</a> </div> </div> <div> </div> <div>I was unable to see this error thrown again, but we may have enough to still fix in the exception mapping code.</div> <div> </div> <div>- Jim</div> <div> </div> </div> <div class="gmail_extra"> <div class="gmail_quote">On Wed, May 24, 2017 at 1:26 PM, Stefan Richthofer <span><<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>></span> wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;"> <div> <div style="font-family: Verdana;font-size: 12.0px;"> <div> <div>Did someone test this on OSX? (reminder: <a href="https://github.com/Stewori/jython" target="_blank">https://github.com/Stewori/jython</a>)</div> <div>Or on Java 7?</div> <div>I just tested on Java 7 and the only test I observe to fail unexpectedly is test_random:</div> <div> </div> <div>test_random crashed -- <type 'exceptions.IOError'>: [Errno 13] Permission denied: '/data/workspace/linux/Jython_extlib/jython/dist/testreports/TEST-test.test_random.WichmannHill_TestBasicOps.xml'</div> <div> </div> <div>The test passes when run individually.</div> <div> </div> <div>However that is on my old laptop running Linux Mint Debian/LMDE2. It seems to be</div> <div>some io error due to access rights and also occurs when running with Java8 on that</div> <div>machine. Note that it passes with Java 8 on my current system. Unless this is due to</div> <div>Java 8_111 vs Java 8_131, I guess it's system dependent. Strange though:</div> <div>worked well before extlib update.</div> <div> </div> <div>Still I'd suggest to get this stuff in for RC-phase, given that the test passes individually.</div> <div>I'd merge this stuff as soon as someone reports OSX results.</div> <div> </div> <div>-Stefan</div> <div> </div> <div> <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Dienstag, 23. Mai 2017 um 23:57 Uhr<br/> <b>Von:</b> "Stefan Richthofer" <<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>><br/> <b>An:</b> "Jim Baker" <<a href="mailto:jim...@py..." onclick="parent.window.location.href='jim...@py...'; return false;" target="_blank">jim...@py...</a>> <div> <div class="h5"><br/> <b>Cc:</b> "Jython Developers" <<a href="mailto:jyt...@li..." onclick="parent.window.location.href='jyt...@li...'; return false;" target="_blank">jyt...@li...</a>><br/> <b>Betreff:</b> Re: [Jython-dev] Updating extlibs</div> </div> </div> <div> <div> <div class="h5"> <div style="font-family: Verdana;font-size: 12.0px;"> <div> <div>Just noticed guava > 20.0 requires Java 8.</div> <div>Strange thing: When building and running Jython on Java 8 with guava 22.0 all regrtests pass fine, but jar-standalone build is bad. Seems like our ant task fails to copy com.google -> org.python.google. Note that I double and triple checked I adjusted build.xml correctly. Is this related to jarjar? Is it maybe not compatible with Java8 jar-files? This might become a problem at some point.</div> <div>Studying guava 22.0 release notes more properly showed that one shall use guava-22.0-android.jar to target Java 7 also on non-Android platforms. With guava-22.0-android.jar, building Jython jar-standalone works well indeed. regrtests also seem to pass then.</div> <div>Ideas?</div> <div>I'll update the linked repo from last email with guava-22.0-android.jar...</div> <div> <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Montag, 22. Mai 2017 um 17:22 Uhr<br/> <b>Von:</b> "Jim Baker" <<a href="mailto:jim...@py..." onclick="parent.window.location.href='jim...@py...'; return false;" target="_blank">jim...@py...</a>><br/> <b>An:</b> "Stefan Richthofer" <<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>><br/> <b>Cc:</b> "Jython Developers" <<a href="mailto:jyt...@li..." onclick="parent.window.location.href='jyt...@li...'; return false;" target="_blank">jyt...@li...</a>><br/> <b>Betreff:</b> Re: [Jython-dev] Updating extlibs</div> <div> <div>These changes look good to me. I will test out your patch, but all of this is in line with similar updates we have made in the past, usually around this time in the dev cycle. <div> </div> <div>I'm glad that moving to Gradle will make this re-pinning to upstream dependencies much easier going forward!</div> </div> <div class="gmail_extra"> <div class="gmail_quote">On Mon, May 22, 2017 at 8:46 AM, Stefan Richthofer <span><<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>></span> wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">I uploaded the mentioned updates to<br/> <a href="https://github.com/Stewori/jython" target="_blank">https://github.com/Stewori/jython</a>.<br/> See detailed changes at<br/> <a href="https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e9499afc6d02267648ac36" target="_blank">https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e9499afc6d02267648ac36</a><br/> <br/> This might not yet work smoothly with Java 7, I will check and adjust that tomorrow.<br/> Some packages were built from source using Java 8 and I'm not sure whether the gradle<br/> scripts always configured Java 7 source compatibility properly.<br/> However if some people could test it, especially on OSX, would be nice.<br/> <br/> Best<br/> <br/> Stefan<br/> <br/> <br/> > Gesendet: Montag, 22. Mai 2017 um 04:07 Uhr<br/> > Von: "Stefan Richthofer" <<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>><br/> > An: "Jython Developers" <<a href="mailto:jyt...@li..." onclick="parent.window.location.href='jyt...@li...'; return false;" target="_blank">jyt...@li...</a>><br/> > Betreff: Updating extlibs <div class="m_-4666966744133675115HOEnZb"> <div class="m_-4666966744133675115h5">><br/> > Hey all,<br/> > I spent some effort to explore feasibility of updating extlibs, especially minor versions (but sometimes even major version, e.g. guava and icu4j).<br/> > My results so far, tested with regrtest on Linux and Windows 10 using Java8 ("okay" means I did not observe additional regrtest failures):<br/> ><br/> > ASM 5.0.4 -> 5.2 okay<br/> > bouncycastle:<br/> > bcpkix-jdk15on-1.54 -> 1.57 okay<br/> > bcprov-jdk15on-1.54 -> 1.57 okay<br/> ><br/> > commons-compress-1.12 -> 1.14 okay<br/> > guava-20.0 -> 22.0rc1 okay<br/> > icu4j-58.1 -> 59_1 okay<br/> > Netty 4.1.6 -> 4.1.11 okay<br/> > java-sizeof-0.0.5 -- still current<br/> > jffi-1.2.13 -> 1.2.15 okay<br/> > jnr-ffi-2.1.0 -> 2.1.5 okay<br/> > jnr-netdb-1.1.6 -- still current<br/> > jnr-posix-3.0.31 -> 3.0.41 okay<br/> > jnr-constants-0.9.5 -> 0.9.9 okay<br/> > New platforms: jffi-aarch64-Linux.jar, jffi-ppc64le-Linux.jar, can be added...?<br/> > Updated various other changed platform specific jars to jffi-1.2.15 (okay as far as tested)<br/> > xercesImpl-2.11.0 -- still current<br/> > jline-2.14.2 -> 2.14.3 okay (didn't try jline-3 this time)<br/> > jarjar-1.4 -- still current<br/> > mysql-connector-java-5.1.6 -> 5.1.42 okay<br/> > postgresql-8.3-603.jdbc4 -> 42.1.1-jre7 okay<br/> ><br/> > ----------These failed, so leaving them as it is:<br/> > Antlr 3.1.3 -> 3.5.2 fails<br/> > junit-4.10 -> 4.12 or 4.11 class file for org.hamcrest.Matcher not found<br/> > (staying with 4.10 for now to avoid new dependency on hamcrest-matcher)<br/> > javax.servlet-api-2.5 -> 3.1.0 fails<br/> > mockrunner (better don't touch; whole structure changed)<br/> > cpptasks (better don't touch)<br/> ><br/> > - will be able to test with Java 7 on Tuesday, because I left my old laptop in the office.<br/> > - will upload a fork containing these updates. Would be good if someone else could also test, especially on OSX.<br/> > Maybe some stuff was not covered by regrtests. However the chance that updates solve issues and that they create issues are probably somewhat equal and I'd prefer to focus on fixing issues with current versions rather than older ones.<br/> > So I'm strongly for getting this in if regrtests go through on Java 7 and OSX. 2.7.1RC-phase will be a good opportunity to confirm workability of these updates. Any concerns?<br/> ><br/> > -Stefan<br/> <br/> ------------------------------------------------------------------------------<br/> Check out the vibrant tech community on one of the world's most<br/> engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a><br/> _______________________________________________<br/> Jython-dev mailing list<br/> <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a><br/> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></div> </div> </blockquote> </div> </div> </div> </div> </div> </div> </div> </div> </div> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot_______________________________________________" target="_blank">http://sdm.link/slashdot_______________________________________________</a> Jython-dev mailing list <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></div> </div> </div> </div> </div> </div> <br/> ------------------------------------------------------------------------------<br/> Check out the vibrant tech community on one of the world's most<br/> engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a><br/> _______________________________________________<br/> Jython-dev mailing list<br/> <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a><br/> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br/> </blockquote> </div> </div> </div> </div> </div> </div></div></body></html> |
|
From: Jim B. <jim...@py...> - 2017-05-27 00:13:07
|
Agreed. It's time for putting this release candidate out! I'm also glad about the timing, because this mean Stefan has a great base to build this summer's work on JyNI. I believe it's technically RC1 still because the last RC was a soft release, but Frank knows those specifics. I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 one last time, just to make sure. Everything looks great! After this we can look into: 1. Finally get jython.org revamped. I suggest the simplicity — and modern look — of GitHub pages, where we can host and then point jython.org accordingly. 2. Switch to the Gradle build that Darjus has been working on 3. Cut over to https://github.com/jython/jython with rewritten history that removes extlib jars for a subsequent release of 2.7.x, where x > 1 (maybe it's 12 for the next release, but we can decide later). Lastly, I also felt it was important to highlight Stefan's contribution to helping finalize 2.7.1, as well as our appreciation to Google for supporting him this summer for the Google Summer of Code. First win for GSOC 2017 in other words. Duly noted as of https://hg.python.org/jython/rev/ab5434be88aa - Jim On May 26, 2017 7:24 PM, "Stefan Richthofer" <Ste...@gm...> wrote: > > You can apply these updates to extlibs > Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8. > > From my point of view we can launch Jython 2.7.1-RC2 now. > > - no open PRs on github left > - no release blockers left apparently except #2487 > - all updates done as far as possible (python std-lib will be next > challenge on this front) > > So, I'd suggest everybody pushes last-minute work and Frank hits the > release-button... :-) > What do you think? > > > Cheers! > > -Stefan > > > *Gesendet:* Freitag, 26. Mai 2017 um 20:16 Uhr > *Von:* "Jim Baker" <jim...@py...> > *An:* "Stefan Richthofer" <Ste...@gm...> > *Cc:* "Jython Developers" <jyt...@li...> > *Betreff:* Re: [Jython-dev] Updating extlibs > Stefan, > > You can apply these updates to extlibs, based on my testing on OSX. More > below. > > > I was able to run the following on both Java 7 and Java 8 on OSX: > > pip/setuptools installation smoke test fully succeeds, using the manual > test described in http://bugs.jython.org/issue2570 (we should look at > automating, at least with a simple bash script) > > regrtest. I did observe flakiness in test_socket_jy, which may require > more rounds of waiting, but it does not appear to happen unless it's run in > the context of other tests, so full runs of the regrtest. (And IIRC, > appeared in the past before extlib update. It has been a well-known flaky > test.) For Java 7, test_codecencodings_tw continues to not completely pass, > almost certainly due to changes in underlying Java support (a bug fix that > was not applied to Java 7). It has nothing to do with these extlib updates. > > Note that test_socket is shaking out some problems, likely due to the > Netty update further refining the exceptions it throws. It's worth noting > that error states are not documented very well for either C sockets or > Netty's rather different support, so we have to explore the implemented > behavior. So one example I saw that should be fixed at some point (possibly > not for 2.7.1, there will always be more bugs, and certainly higher > priority ones IMHO at this time): > > [exec] Unhandled exception in thread started by <bound method > BasicTCPTest.clientRun of testShutdown (test.test_socket.BasicTCPTest)> > [exec] Traceback (most recent call last): > [exec] File "/Users/jbaker/jythondev/jytho > n-extlibs/dist/Lib/test/test_socket.py", line 186, in clientRun > [exec] self.clientSetUp() > [exec] File "/Users/jbaker/jythondev/jytho > n-extlibs/dist/Lib/test/test_socket.py", line 246, in clientSetUp > [exec] self.cli.connect((self.HOST, self.PORT)) > [exec] File "/Users/jbaker/jythondev/jytho > n-extlibs/dist/Lib/_socket.py", line 1441, in meth > [exec] return getattr(self._sock,name)(*args) > [exec] File "/Users/jbaker/jythondev/jytho > n-extlibs/dist/Lib/_socket.py", line 935, in connect > [exec] self._connect(addr) > [exec] File "/Users/jbaker/jythondev/jytho > n-extlibs/dist/Lib/_socket.py", line 911, in _connect > [exec] self._handle_channel_future(self.connect_future, > "connect") > [exec] File "/Users/jbaker/jythondev/jytho > n-extlibs/dist/Lib/_socket.py", line 384, in handle_exception > [exec] raise _map_exception(jlx) > [exec] _socket.error: [Errno -1] Unmapped exception: > io.netty.channel.AbstractChannel$AnnotatedSocketException: Invalid > argument: localhost/127.0.0.1:50100 > > I was unable to see this error thrown again, but we may have enough to > still fix in the exception mapping code. > > - Jim > > > On Wed, May 24, 2017 at 1:26 PM, Stefan Richthofer < > Ste...@gm...> wrote: >> >> Did someone test this on OSX? (reminder: https://github.com/Stewori/jyt >> hon) >> Or on Java 7? >> I just tested on Java 7 and the only test I observe to fail unexpectedly >> is test_random: >> >> test_random crashed -- <type 'exceptions.IOError'>: [Errno 13] Permission >> denied: '/data/workspace/linux/Jython_extlib/jython/dist/testreports >> /TEST-test.test_random.WichmannHill_TestBasicOps.xml' >> >> The test passes when run individually. >> >> However that is on my old laptop running Linux Mint Debian/LMDE2. It >> seems to be >> some io error due to access rights and also occurs when running with >> Java8 on that >> machine. Note that it passes with Java 8 on my current system. Unless >> this is due to >> Java 8_111 vs Java 8_131, I guess it's system dependent. Strange though: >> worked well before extlib update. >> >> Still I'd suggest to get this stuff in for RC-phase, given that the test >> passes individually. >> I'd merge this stuff as soon as someone reports OSX results. >> >> -Stefan >> >> >> *Gesendet:* Dienstag, 23. Mai 2017 um 23:57 Uhr >> *Von:* "Stefan Richthofer" <Ste...@gm...> >> *An:* "Jim Baker" <jim...@py...> >> >> *Cc:* "Jython Developers" <jyt...@li...> >> *Betreff:* Re: [Jython-dev] Updating extlibs >> Just noticed guava > 20.0 requires Java 8. >> Strange thing: When building and running Jython on Java 8 with guava 22.0 >> all regrtests pass fine, but jar-standalone build is bad. Seems like our >> ant task fails to copy com.google -> org.python.google. Note that I double >> and triple checked I adjusted build.xml correctly. Is this related to >> jarjar? Is it maybe not compatible with Java8 jar-files? This might become >> a problem at some point. >> Studying guava 22.0 release notes more properly showed that one shall use >> guava-22.0-android.jar to target Java 7 also on non-Android platforms. With >> guava-22.0-android.jar, building Jython jar-standalone works well indeed. >> regrtests also seem to pass then. >> Ideas? >> I'll update the linked repo from last email with guava-22.0-android.jar... >> >> *Gesendet:* Montag, 22. Mai 2017 um 17:22 Uhr >> *Von:* "Jim Baker" <jim...@py...> >> *An:* "Stefan Richthofer" <Ste...@gm...> >> *Cc:* "Jython Developers" <jyt...@li...> >> *Betreff:* Re: [Jython-dev] Updating extlibs >> These changes look good to me. I will test out your patch, but all of >> this is in line with similar updates we have made in the past, usually >> around this time in the dev cycle. >> >> I'm glad that moving to Gradle will make this re-pinning to upstream >> dependencies much easier going forward! >> >> On Mon, May 22, 2017 at 8:46 AM, Stefan Richthofer < >> Ste...@gm...> wrote: >>> >>> I uploaded the mentioned updates to >>> https://github.com/Stewori/jython. >>> See detailed changes at >>> https://github.com/Stewori/jython/commit/ee2b1263306f779bf8e >>> 9499afc6d02267648ac36 >>> >>> This might not yet work smoothly with Java 7, I will check and adjust >>> that tomorrow. >>> Some packages were built from source using Java 8 and I'm not sure >>> whether the gradle >>> scripts always configured Java 7 source compatibility properly. >>> However if some people could test it, especially on OSX, would be nice. >>> >>> Best >>> >>> Stefan >>> >>> >>> > Gesendet: Montag, 22. Mai 2017 um 04:07 Uhr >>> > Von: "Stefan Richthofer" <Ste...@gm...> >>> > An: "Jython Developers" <jyt...@li...> >>> > Betreff: Updating extlibs >>> > >>> > Hey all, >>> > I spent some effort to explore feasibility of updating extlibs, >>> especially minor versions (but sometimes even major version, e.g. guava and >>> icu4j). >>> > My results so far, tested with regrtest on Linux and Windows 10 using >>> Java8 ("okay" means I did not observe additional regrtest failures): >>> > >>> > ASM 5.0.4 -> 5.2 okay >>> > bouncycastle: >>> > bcpkix-jdk15on-1.54 -> 1.57 okay >>> > bcprov-jdk15on-1.54 -> 1.57 okay >>> > >>> > commons-compress-1.12 -> 1.14 okay >>> > guava-20.0 -> 22.0rc1 okay >>> > icu4j-58.1 -> 59_1 okay >>> > Netty 4.1.6 -> 4.1.11 okay >>> > java-sizeof-0.0.5 -- still current >>> > jffi-1.2.13 -> 1.2.15 okay >>> > jnr-ffi-2.1.0 -> 2.1.5 okay >>> > jnr-netdb-1.1.6 -- still current >>> > jnr-posix-3.0.31 -> 3.0.41 okay >>> > jnr-constants-0.9.5 -> 0.9.9 okay >>> > New platforms: jffi-aarch64-Linux.jar, jffi-ppc64le-Linux.jar, can be >>> added...? >>> > Updated various other changed platform specific jars to jffi-1.2.15 >>> (okay as far as tested) >>> > xercesImpl-2.11.0 -- still current >>> > jline-2.14.2 -> 2.14.3 okay (didn't try jline-3 >>> this time) >>> > jarjar-1.4 -- still current >>> > mysql-connector-java-5.1.6 -> 5.1.42 okay >>> > postgresql-8.3-603.jdbc4 -> 42.1.1-jre7 okay >>> > >>> > ----------These failed, so leaving them as it is: >>> > Antlr 3.1.3 -> 3.5.2 fails >>> > junit-4.10 -> 4.12 or 4.11 class file for >>> org.hamcrest.Matcher not found >>> > (staying with 4.10 for now to avoid new dependency on hamcrest-matcher) >>> > javax.servlet-api-2.5 -> 3.1.0 fails >>> > mockrunner (better don't touch; whole structure changed) >>> > cpptasks (better don't touch) >>> > >>> > - will be able to test with Java 7 on Tuesday, because I left my old >>> laptop in the office. >>> > - will upload a fork containing these updates. Would be good if >>> someone else could also test, especially on OSX. >>> > Maybe some stuff was not covered by regrtests. However the chance that >>> updates solve issues and that they create issues are probably somewhat >>> equal and I'd prefer to focus on fixing issues with current versions rather >>> than older ones. >>> > So I'm strongly for getting this in if regrtests go through on Java 7 >>> and OSX. 2.7.1RC-phase will be a good opportunity to confirm workability of >>> these updates. Any concerns? >>> > >>> > -Stefan >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most engaging >> tech sites, Slashdot.org! http://sdm.link/slashdot______ >> _________________________________________ Jython-dev mailing list >> Jyt...@li... https://lists.sourceforge.net/ >> lists/listinfo/jython-dev >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > > |
|
From: Jeff A. <ja...@fa...> - 2017-05-27 07:34:17
|
Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to find we've all feel "done"at the same time :) Small typo in your front page: "many others to thanks". I have a weak preference for calling it RC2 given there was change after RC1. I think RC1 still identifies a release, even if it was announced softly, and what we have now is different. There's a bit more to cutting over to Git than declaring it so. I've been watching CPython do this with the corner of one eye. We will have both bugs.jython.org and Git pull requests for a while ... essentially forever. There was some integration work (which we should steal, but that depends, I suspect, on upgrading the tracker) and conventions for how to refer to one from the other. It was tough at points because of disagreement on how it were best done, but we can just go along with their conclusion. And s/bpo/bjo/. Jeff Allen On 27/05/2017 01:12, Jim Baker wrote: > Agreed. It's time for putting this release candidate out! I'm also > glad about the timing, because this mean Stefan has a great base to > build this summer's work on JyNI. I believe it's technically RC1 still > because the last RC was a soft release, but Frank knows those specifics. > > I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 > <http://bugs.jython.org/issue2570> one last time, just to make sure. > Everything looks great! > > After this we can look into: > > 1. Finally get jython.org <http://jython.org> revamped. I suggest the > simplicity — and modern look — of GitHub pages, where we can host and > then point jython.org <http://jython.org> accordingly. > 2. Switch to the Gradle build that Darjus has been working on > 3. Cut over to https://github.com/jython/jython with rewritten history > that removes extlib jars for a subsequent release of 2.7.x, where x > > 1 (maybe it's 12 for the next release, but we can decide later). > > Lastly, I also felt it was important to highlight Stefan's > contribution to helping finalize 2.7.1, as well as our appreciation to > Google for supporting him this summer for the Google Summer of Code. > First win for GSOC 2017 in other words. Duly noted as of > https://hg.python.org/jython/rev/ab5434be88aa > > - Jim > > > > On May 26, 2017 7:24 PM, "Stefan Richthofer" <Ste...@gm... > <mailto:Ste...@gm...>> wrote: > > > You can apply these updates to extlibs > Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8 > <https://hg.python.org/jython/rev/f6b3ddbc1df8>. > From my point of view we can launch Jython 2.7.1-RC2 now. > - no open PRs on github left > - no release blockers left apparently except #2487 > - all updates done as far as possible (python std-lib will be next > challenge on this front) > So, I'd suggest everybody pushes last-minute work and Frank hits > the release-button... :-) > What do you think? > Cheers! > -Stefan > <snip> |
|
From: Adam B. <ada...@gm...> - 2017-05-27 09:07:45
|
I know I'm a lurker and not an active dev, but I'd prefer the rc2 name as well, fwiw. Cheers Adam On 27 May 2017 at 15:33, Jeff Allen <ja...@fa...> wrote: > Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to > find we've all feel "done"at the same time :) > > Small typo in your front page: "many others to thanks". > > I have a weak preference for calling it RC2 given there was change after > RC1. I think RC1 still identifies a release, even if it was announced > softly, and what we have now is different. > > There's a bit more to cutting over to Git than declaring it so. I've been > watching CPython do this with the corner of one eye. We will have both > bugs.jython.org and Git pull requests for a while ... essentially > forever. There was some integration work (which we should steal, but that > depends, I suspect, on upgrading the tracker) and conventions for how to > refer to one from the other. It was tough at points because of disagreement > on how it were best done, but we can just go along with their conclusion. > And s/bpo/bjo/. > > Jeff Allen > > On 27/05/2017 01:12, Jim Baker wrote: > >> Agreed. It's time for putting this release candidate out! I'm also glad >> about the timing, because this mean Stefan has a great base to build this >> summer's work on JyNI. I believe it's technically RC1 still because the >> last RC was a soft release, but Frank knows those specifics. >> >> I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 < >> http://bugs.jython.org/issue2570> one last time, just to make sure. >> Everything looks great! >> >> After this we can look into: >> >> 1. Finally get jython.org <http://jython.org> revamped. I suggest the >> simplicity — and modern look — of GitHub pages, where we can host and then >> point jython.org <http://jython.org> accordingly. >> 2. Switch to the Gradle build that Darjus has been working on >> 3. Cut over to https://github.com/jython/jython with rewritten history >> that removes extlib jars for a subsequent release of 2.7.x, where x > 1 >> (maybe it's 12 for the next release, but we can decide later). >> >> Lastly, I also felt it was important to highlight Stefan's contribution >> to helping finalize 2.7.1, as well as our appreciation to Google for >> supporting him this summer for the Google Summer of Code. First win for >> GSOC 2017 in other words. Duly noted as of https://hg.python.org/jython/r >> ev/ab5434be88aa >> >> - Jim >> >> >> >> On May 26, 2017 7:24 PM, "Stefan Richthofer" <Ste...@gm... >> <mailto:Ste...@gm...>> wrote: >> >> > You can apply these updates to extlibs >> Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8 >> <https://hg.python.org/jython/rev/f6b3ddbc1df8>. >> From my point of view we can launch Jython 2.7.1-RC2 now. >> - no open PRs on github left >> - no release blockers left apparently except #2487 >> - all updates done as far as possible (python std-lib will be next >> challenge on this front) >> So, I'd suggest everybody pushes last-minute work and Frank hits >> the release-button... :-) >> What do you think? >> Cheers! >> -Stefan >> >> <snip> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Jim B. <jim...@py...> - 2017-05-27 17:46:07
|
Updated README to state RC2, plus fixed the typo. Thanks for the feedback! Agreed that getting on github will not be the most minor fix (!), but it will be worth the effort. I do like Mercurial, and very much appreciate the Hg team's help in moving Jython to hg.python.org from Subversion. Nonetheless, we found out in using Mercurial for the last 5 or so years for Jython development that it didn't match our development processes. It's both time to move on, and join CPython upstream in its dev processes. On Sat, May 27, 2017 at 5:07 AM, Adam Burke <ada...@gm...> wrote: > I know I'm a lurker and not an active dev, but I'd prefer the rc2 name as > well, fwiw. > > Cheers > Adam > > On 27 May 2017 at 15:33, Jeff Allen <ja...@fa...> wrote: > >> Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to >> find we've all feel "done"at the same time :) >> >> Small typo in your front page: "many others to thanks". >> >> I have a weak preference for calling it RC2 given there was change after >> RC1. I think RC1 still identifies a release, even if it was announced >> softly, and what we have now is different. >> >> There's a bit more to cutting over to Git than declaring it so. I've been >> watching CPython do this with the corner of one eye. We will have both >> bugs.jython.org and Git pull requests for a while ... essentially >> forever. There was some integration work (which we should steal, but that >> depends, I suspect, on upgrading the tracker) and conventions for how to >> refer to one from the other. It was tough at points because of disagreement >> on how it were best done, but we can just go along with their conclusion. >> And s/bpo/bjo/. >> >> Jeff Allen >> >> On 27/05/2017 01:12, Jim Baker wrote: >> >>> Agreed. It's time for putting this release candidate out! I'm also glad >>> about the timing, because this mean Stefan has a great base to build this >>> summer's work on JyNI. I believe it's technically RC1 still because the >>> last RC was a soft release, but Frank knows those specifics. >>> >>> I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 < >>> http://bugs.jython.org/issue2570> one last time, just to make sure. >>> Everything looks great! >>> >>> After this we can look into: >>> >>> 1. Finally get jython.org <http://jython.org> revamped. I suggest the >>> simplicity — and modern look — of GitHub pages, where we can host and then >>> point jython.org <http://jython.org> accordingly. >>> 2. Switch to the Gradle build that Darjus has been working on >>> 3. Cut over to https://github.com/jython/jython with rewritten history >>> that removes extlib jars for a subsequent release of 2.7.x, where x > 1 >>> (maybe it's 12 for the next release, but we can decide later). >>> >>> Lastly, I also felt it was important to highlight Stefan's contribution >>> to helping finalize 2.7.1, as well as our appreciation to Google for >>> supporting him this summer for the Google Summer of Code. First win for >>> GSOC 2017 in other words. Duly noted as of >>> https://hg.python.org/jython/rev/ab5434be88aa >>> >>> - Jim >>> >>> >>> >>> On May 26, 2017 7:24 PM, "Stefan Richthofer" <Ste...@gm... >>> <mailto:Ste...@gm...>> wrote: >>> >>> > You can apply these updates to extlibs >>> Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8 >>> <https://hg.python.org/jython/rev/f6b3ddbc1df8>. >>> From my point of view we can launch Jython 2.7.1-RC2 now. >>> - no open PRs on github left >>> - no release blockers left apparently except #2487 >>> - all updates done as far as possible (python std-lib will be next >>> challenge on this front) >>> So, I'd suggest everybody pushes last-minute work and Frank hits >>> the release-button... :-) >>> What do you think? >>> Cheers! >>> -Stefan >>> >>> <snip> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > |
|
From: <fwi...@gm...> - 2017-05-27 18:43:57
|
Great news, and amazing work everyone! I'll get the soft release together this weekend. If there are no troubles, I'll get the hard RC2 out next week. On May 27, 2017 10:46, "Jim Baker" <jim...@py...> wrote: Updated README to state RC2, plus fixed the typo. Thanks for the feedback! Agreed that getting on github will not be the most minor fix (!), but it will be worth the effort. I do like Mercurial, and very much appreciate the Hg team's help in moving Jython to hg.python.org from Subversion. Nonetheless, we found out in using Mercurial for the last 5 or so years for Jython development that it didn't match our development processes. It's both time to move on, and join CPython upstream in its dev processes. On Sat, May 27, 2017 at 5:07 AM, Adam Burke <ada...@gm...> wrote: > I know I'm a lurker and not an active dev, but I'd prefer the rc2 name as > well, fwiw. > > Cheers > Adam > > On 27 May 2017 at 15:33, Jeff Allen <ja...@fa...> wrote: > >> Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to >> find we've all feel "done"at the same time :) >> >> Small typo in your front page: "many others to thanks". >> >> I have a weak preference for calling it RC2 given there was change after >> RC1. I think RC1 still identifies a release, even if it was announced >> softly, and what we have now is different. >> >> There's a bit more to cutting over to Git than declaring it so. I've been >> watching CPython do this with the corner of one eye. We will have both >> bugs.jython.org and Git pull requests for a while ... essentially >> forever. There was some integration work (which we should steal, but that >> depends, I suspect, on upgrading the tracker) and conventions for how to >> refer to one from the other. It was tough at points because of disagreement >> on how it were best done, but we can just go along with their conclusion. >> And s/bpo/bjo/. >> >> Jeff Allen >> >> On 27/05/2017 01:12, Jim Baker wrote: >> >>> Agreed. It's time for putting this release candidate out! I'm also glad >>> about the timing, because this mean Stefan has a great base to build this >>> summer's work on JyNI. I believe it's technically RC1 still because the >>> last RC was a soft release, but Frank knows those specifics. >>> >>> I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 < >>> http://bugs.jython.org/issue2570> one last time, just to make sure. >>> Everything looks great! >>> >>> After this we can look into: >>> >>> 1. Finally get jython.org <http://jython.org> revamped. I suggest the >>> simplicity — and modern look — of GitHub pages, where we can host and then >>> point jython.org <http://jython.org> accordingly. >>> 2. Switch to the Gradle build that Darjus has been working on >>> 3. Cut over to https://github.com/jython/jython with rewritten history >>> that removes extlib jars for a subsequent release of 2.7.x, where x > 1 >>> (maybe it's 12 for the next release, but we can decide later). >>> >>> Lastly, I also felt it was important to highlight Stefan's contribution >>> to helping finalize 2.7.1, as well as our appreciation to Google for >>> supporting him this summer for the Google Summer of Code. First win for >>> GSOC 2017 in other words. Duly noted as of >>> https://hg.python.org/jython/rev/ab5434be88aa >>> >>> - Jim >>> >>> >>> >>> On May 26, 2017 7:24 PM, "Stefan Richthofer" <Ste...@gm... >>> <mailto:Ste...@gm...>> wrote: >>> >>> > You can apply these updates to extlibs >>> Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8 >>> <https://hg.python.org/jython/rev/f6b3ddbc1df8>. >>> From my point of view we can launch Jython 2.7.1-RC2 now. >>> - no open PRs on github left >>> - no release blockers left apparently except #2487 >>> - all updates done as far as possible (python std-lib will be next >>> challenge on this front) >>> So, I'd suggest everybody pushes last-minute work and Frank hits >>> the release-button... :-) >>> What do you think? >>> Cheers! >>> -Stefan >>> >>> <snip> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Jython-dev mailing list Jyt...@li... https://lists.sourceforge.net/lists/listinfo/jython-dev |
|
From: Stefan R. <Ste...@gm...> - 2017-05-28 18:11:41
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div> <div>> Agreed that getting on github will not be the most minor fix</div> <div><br/> It occurred to me that this change actually aligns with our focus shift to Jython 3. Maybe we can benefit from this by setting up the new workflow only for Jython 3. Then it would be kind of a reboot rather than a (potentially painful) migration. It would naturaly sort out Jython 3 stuff from Jython 2 stuff. (We could even consider to track Jython 3 issues on github and continue bjo just for Jython 2.) Think about it.</div> <div> </div> <div> </div> <div>> I also felt it was important to highlight Stefan's contribution to helping finalize 2.7.1</div> <div><br/> It's a great honor for me to be mentioned for this. Thank you very much!<br/> Looking at ACKNOWLEDGEMENTS I found that the file does not explicitly display who is actually core-developing Jython right now. Jeff, Jim, Darjus and Frank who are putting a lot of work into Jython (or did so in the last years) are mentioned randomly between all contributors, including persons with really minimal contributions (don't get me wrong - every contribution is very valuable!). While this is a very modest attitude I think the (active) core-dev team should be explicitly named somewhere at the beginning of the file, not lastly because users might need this info to assess who to ask. Also - maybe I overlooked it - it is nowhere stated that Frank is the project lead. This should be made clear IMO. In case we decided to add such a section I'd suggest to also mention James Mudd, at least for this release, because he spent significantly more work on Jython than the average contributor.</div> <div> </div> <div> </div> <div>> I'll get the soft release together this weekend. If there are no troubles, I'll get the hard RC2 out next week.</div> <div><br/> Looking forward to it! Thanks a lot.</div> <div> </div> <div><br/> Best regards</div> <div> </div> <div>-Stefan</div> </div> <div> </div> <div> </div> <div> <div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);"> <div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Samstag, 27. Mai 2017 um 20:43 Uhr<br/> <b>Von:</b> "fwi...@gm..." <fwi...@gm...><br/> <b>An:</b> "Jim Baker" <jim...@py...><br/> <b>Cc:</b> "Jython Developers" <jyt...@li...><br/> <b>Betreff:</b> Re: [Jython-dev] 2.7.1rc, to infinity and beyond!</div> <div> <div> <div>Great news, and amazing work everyone! I'll get the soft release together this weekend. If there are no troubles, I'll get the hard RC2 out next week. <div class="gmail_extra"> <div class="gmail_quote">On May 27, 2017 10:46, "Jim Baker" <<a href="mailto:jim...@py..." onclick="parent.window.location.href='jim...@py...'; return false;" target="_blank">jim...@py...</a>> wrote: <blockquote class="quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;"> <div>Updated README to state RC2, plus fixed the typo. Thanks for the feedback! <div> </div> <div>Agreed that getting on github will not be the most minor fix (!), but it will be worth the effort. I do like Mercurial, and very much appreciate the Hg team's help in moving Jython to <a href="http://hg.python.org" target="_blank">hg.python.org</a> from Subversion. Nonetheless, we found out in using Mercurial for the last 5 or so years for Jython development that it didn't match our development processes. It's both time to move on, and join CPython upstream in its dev processes.</div> </div> <div class="elided-text"> <div class="gmail_extra"> <div class="gmail_quote">On Sat, May 27, 2017 at 5:07 AM, Adam Burke <span><<a href="mailto:ada...@gm..." onclick="parent.window.location.href='ada...@gm...'; return false;" target="_blank">ada...@gm...</a>></span> wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;"> <div><span style="font-size: 12.8px;">I know I'm a lurker and not an active dev, but I'd prefer the rc2 name as well, fwiw.</span> <div style="font-size: 12.8px;"> </div> <div style="font-size: 12.8px;">Cheers</div> <div style="font-size: 12.8px;"><span class="m_8922591695867343507HOEnZb"><font color="#888888">Adam</font></span></div> </div> <div class="m_8922591695867343507HOEnZb"> <div class="m_8922591695867343507h5"> <div class="gmail_extra"> <div class="gmail_quote">On 27 May 2017 at 15:33, Jeff Allen <span><<a href="mailto:ja...@fa..." onclick="parent.window.location.href='ja...@fa...'; return false;" target="_blank">ja...@fa...</a>></span> wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to find we've all feel "done"at the same time :)<br/> <br/> Small typo in your front page: "many others to thanks".<br/> <br/> I have a weak preference for calling it RC2 given there was change after RC1. I think RC1 still identifies a release, even if it was announced softly, and what we have now is different.<br/> <br/> There's a bit more to cutting over to Git than declaring it so. I've been watching CPython do this with the corner of one eye. We will have both <a href="http://bugs.jython.org" target="_blank">bugs.jython.org</a> and Git pull requests for a while ... essentially forever. There was some integration work (which we should steal, but that depends, I suspect, on upgrading the tracker) and conventions for how to refer to one from the other. It was tough at points because of disagreement on how it were best done, but we can just go along with their conclusion. And s/bpo/bjo/.<br/> <br/> Jeff Allen<br/> <br/> On 27/05/2017 01:12, Jim Baker wrote: <blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">Agreed. It's time for putting this release candidate out! I'm also glad about the timing, because this mean Stefan has a great base to build this summer's work on JyNI. I believe it's technically RC1 still because the last RC was a soft release, but Frank knows those specifics.<br/> <br/> I just ran the "yolk smoke test" from <a href="http://bugs.jython.org/issue2570" target="_blank">http://bugs.jython.org/issue2570</a> <<a href="http://bugs.jython.org/issue2570" target="_blank">http://bugs.jython.org/issue2570</a>> one last time, just to make sure. Everything looks great!<br/> <br/> After this we can look into:<br/> <br/> 1. Finally get <a href="http://jython.org" target="_blank">jython.org</a> <<a href="http://jython.org" target="_blank">http://jython.org</a>> revamped. I suggest the simplicity — and modern look — of GitHub pages, where we can host and then point <a href="http://jython.org" target="_blank">jython.org</a> <<a href="http://jython.org" target="_blank">http://jython.org</a>> accordingly.<br/> 2. Switch to the Gradle build that Darjus has been working on<br/> 3. Cut over to <a href="https://github.com/jython/jython" target="_blank">https://github.com/jython/jython</a> with rewritten history that removes extlib jars for a subsequent release of 2.7.x, where x > 1 (maybe it's 12 for the next release, but we can decide later).<br/> <br/> Lastly, I also felt it was important to highlight Stefan's contribution to helping finalize 2.7.1, as well as our appreciation to Google for supporting him this summer for the Google Summer of Code. First win for GSOC 2017 in other words. Duly noted as of <a href="https://hg.python.org/jython/rev/ab5434be88aa" target="_blank">https://hg.python.org/jython/rev/ab5434be88aa</a><br/> <br/> - Jim<br/> <br/> <br/> <br/> On May 26, 2017 7:24 PM, "Stefan Richthofer" <<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a> <mailto:<a href="mailto:Ste...@gm..." onclick="parent.window.location.href='Ste...@gm...'; return false;" target="_blank">Ste...@gm...</a>>> wrote:<br/> <br/> > You can apply these updates to extlibs<br/> Done as of <a href="https://hg.python.org/jython/rev/f6b3ddbc1df8" target="_blank">https://hg.python.org/jython/rev/f6b3ddbc1df8</a><br/> <<a href="https://hg.python.org/jython/rev/f6b3ddbc1df8" target="_blank">https://hg.python.org/jython/rev/f6b3ddbc1df8</a>>.<br/> From my point of view we can launch Jython 2.7.1-RC2 now.<br/> - no open PRs on github left<br/> - no release blockers left apparently except #2487<br/> - all updates done as far as possible (python std-lib will be next<br/> challenge on this front)<br/> So, I'd suggest everybody pushes last-minute work and Frank hits<br/> the release-button... :-)<br/> What do you think?<br/> Cheers!<br/> -Stefan<br/> </blockquote> <snip><br/> <br/> ------------------------------------------------------------------------------<br/> Check out the vibrant tech community on one of the world's most<br/> engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a><br/> _______________________________________________<br/> Jython-dev mailing list<br/> <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a><br/> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></blockquote> </div> </div> </div> </div> <br/> ------------------------------------------------------------------------------<br/> Check out the vibrant tech community on one of the world's most<br/> engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a><br/> _______________________________________________<br/> Jython-dev mailing list<br/> <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a><br/> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br/> </blockquote> </div> </div> </div> <br/> ------------------------------------------------------------------------------<br/> Check out the vibrant tech community on one of the world's most<br/> engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot" target="_blank">http://sdm.link/slashdot</a><br/> _______________________________________________<br/> Jython-dev mailing list<br/> <a href="mailto:Jyt...@li..." onclick="parent.window.location.href='Jyt...@li...'; return false;" target="_blank">Jyt...@li...</a><br/> <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br/> </blockquote> </div> </div> </div> </div> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot_______________________________________________" target="_blank">http://sdm.link/slashdot_______________________________________________</a> Jython-dev mailing list Jyt...@li... <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></div> </div> </div> </div></div></body></html> |
|
From: James M. <jam...@gm...> - 2017-05-28 20:45:21
|
Just a few comments from my point of view. I think moving to a Github based workflow will help to attract more contributors to Jython. I just think more people are familiar with the workflow, so it's less effort to get involved, even minor things like having to sign up to bugs.jython.org might put people off. Having said that I really hope more people get involved. I have really enjoyed putting some work into Jython, and have got to investigate some interesting bugs which has been really fun. I think its a unique kind of project which is really interesting to work on, and all the other contributors seem to be really friendly and helpful. I hope to keep contributing in the future when time allows. Also thanks to Stefan for the comments, and the great discussion on many of the bugs fixed over the last few months, as well as merging many of my suggested patches. Looking forward to seeing the RC2, and hopefully soon after the final release. James On 28 May 2017 at 19:11, Stefan Richthofer <Ste...@gm...> wrote: > > Agreed that getting on github will not be the most minor fix > > It occurred to me that this change actually aligns with our focus shift to > Jython 3. Maybe we can benefit from this by setting up the new workflow > only for Jython 3. Then it would be kind of a reboot rather than a > (potentially painful) migration. It would naturaly sort out Jython 3 stuff > from Jython 2 stuff. (We could even consider to track Jython 3 issues on > github and continue bjo just for Jython 2.) Think about it. > > > > I also felt it was important to highlight Stefan's contribution to > helping finalize 2.7.1 > > It's a great honor for me to be mentioned for this. Thank you very much! > Looking at ACKNOWLEDGEMENTS I found that the file does not explicitly > display who is actually core-developing Jython right now. Jeff, Jim, Darjus > and Frank who are putting a lot of work into Jython (or did so in the last > years) are mentioned randomly between all contributors, including persons > with really minimal contributions (don't get me wrong - every contribution > is very valuable!). While this is a very modest attitude I think the > (active) core-dev team should be explicitly named somewhere at the > beginning of the file, not lastly because users might need this info to > assess who to ask. Also - maybe I overlooked it - it is nowhere stated that > Frank is the project lead. This should be made clear IMO. In case we > decided to add such a section I'd suggest to also mention James Mudd, at > least for this release, because he spent significantly more work on Jython > than the average contributor. > > > > I'll get the soft release together this weekend. If there are no > troubles, I'll get the hard RC2 out next week. > > Looking forward to it! Thanks a lot. > > > Best regards > > -Stefan > > > > *Gesendet:* Samstag, 27. Mai 2017 um 20:43 Uhr > *Von:* "fwi...@gm..." <fwi...@gm...> > *An:* "Jim Baker" <jim...@py...> > *Cc:* "Jython Developers" <jyt...@li...> > *Betreff:* Re: [Jython-dev] 2.7.1rc, to infinity and beyond! > Great news, and amazing work everyone! I'll get the soft release together > this weekend. If there are no troubles, I'll get the hard RC2 out next > week. > > On May 27, 2017 10:46, "Jim Baker" <jim...@py...> wrote: > > Updated README to state RC2, plus fixed the typo. Thanks for the feedback! > > Agreed that getting on github will not be the most minor fix (!), but it > will be worth the effort. I do like Mercurial, and very much appreciate the > Hg team's help in moving Jython to hg.python.org from Subversion. > Nonetheless, we found out in using Mercurial for the last 5 or so years for > Jython development that it didn't match our development processes. It's > both time to move on, and join CPython upstream in its dev processes. > > On Sat, May 27, 2017 at 5:07 AM, Adam Burke <ada...@gm...> > wrote: >> >> I know I'm a lurker and not an active dev, but I'd prefer the rc2 name as >> well, fwiw. >> >> Cheers >> Adam >> >> On 27 May 2017 at 15:33, Jeff Allen <ja...@fa...> wrote: >>> >>> Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to >>> find we've all feel "done"at the same time :) >>> >>> Small typo in your front page: "many others to thanks". >>> >>> I have a weak preference for calling it RC2 given there was change after >>> RC1. I think RC1 still identifies a release, even if it was announced >>> softly, and what we have now is different. >>> >>> There's a bit more to cutting over to Git than declaring it so. I've >>> been watching CPython do this with the corner of one eye. We will have both >>> bugs.jython.org and Git pull requests for a while ... essentially >>> forever. There was some integration work (which we should steal, but that >>> depends, I suspect, on upgrading the tracker) and conventions for how to >>> refer to one from the other. It was tough at points because of disagreement >>> on how it were best done, but we can just go along with their conclusion. >>> And s/bpo/bjo/. >>> >>> Jeff Allen >>> >>> On 27/05/2017 01:12, Jim Baker wrote: >>>> >>>> Agreed. It's time for putting this release candidate out! I'm also glad >>>> about the timing, because this mean Stefan has a great base to build this >>>> summer's work on JyNI. I believe it's technically RC1 still because the >>>> last RC was a soft release, but Frank knows those specifics. >>>> >>>> I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 >>>> <http://bugs.jython.org/issue2570> one last time, just to make sure. >>>> Everything looks great! >>>> >>>> After this we can look into: >>>> >>>> 1. Finally get jython.org <http://jython.org> revamped. I suggest the >>>> simplicity — and modern look — of GitHub pages, where we can host and then >>>> point jython.org <http://jython.org> accordingly. >>>> 2. Switch to the Gradle build that Darjus has been working on >>>> 3. Cut over to https://github.com/jython/jython with rewritten history >>>> that removes extlib jars for a subsequent release of 2.7.x, where x > 1 >>>> (maybe it's 12 for the next release, but we can decide later). >>>> >>>> Lastly, I also felt it was important to highlight Stefan's contribution >>>> to helping finalize 2.7.1, as well as our appreciation to Google for >>>> supporting him this summer for the Google Summer of Code. First win for >>>> GSOC 2017 in other words. Duly noted as of >>>> https://hg.python.org/jython/rev/ab5434be88aa >>>> >>>> - Jim >>>> >>>> >>>> >>>> On May 26, 2017 7:24 PM, "Stefan Richthofer" <Ste...@gm... >>>> <mailto:Ste...@gm...>> wrote: >>>> >>>> > You can apply these updates to extlibs >>>> Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8 >>>> <https://hg.python.org/jython/rev/f6b3ddbc1df8>. >>>> From my point of view we can launch Jython 2.7.1-RC2 now. >>>> - no open PRs on github left >>>> - no release blockers left apparently except #2487 >>>> - all updates done as far as possible (python std-lib will be next >>>> challenge on this front) >>>> So, I'd suggest everybody pushes last-minute work and Frank hits >>>> the release-button... :-) >>>> What do you think? >>>> Cheers! >>>> -Stefan >>>> >>> >>> <snip> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most engaging > tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ Jython-dev mailing list > Jyt...@li... https://lists.sourceforge.net/ > lists/listinfo/jython-dev > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > |
|
From: Jeff A. <ja...@fa...> - 2017-05-28 23:09:56
|
+1 on Stefan's suggestion that we simply start as we mean to go on with Jython 3 on GitHub. We still must choose a workflow and make it known. This might be a change of practice for those of us with direct commit rights, away from commit-then-review, to something based on PRs. I was always a bit surprised we did not have such a two-step process with Mercurial. Concerning identifying the value of individuals' contributions, I think we enter a minefield. It seems to be the Python way that we're all just names in a big flat acknowledgements file, however large or small our contribution. I saw this principle enunciated by Guido on python-dev. (Sorry, can't find it now.) Oh, now I look, it's loosely what the ACKS file itself says. I think it more practical to talk about what trust the project accords someone, which brings us back to workflow. On CPython there's an identified set of core developers who have the right (and are relied upon) to review others' contributions and commit them to the project repository -- being trusted to know their own competence. That is worth being clearer about for Jython, especially if someone has commit rights in practice but we don't expect them to review PRs/patches. On GitHub, some of us are members and others owners, but I don't know what is intended by that. There was some debate in CPython about the new workflow, whether code devs could review and accept their own work. I think there should normally be at least the opportunity for peer review if work is a large change ... something like I did for the 2.7.1 changes to the buffer interface and UTF-8 fix. In the unique case of the project lead, I believe Frank's status is a PSF appointment. I have seen that in documentation somewhere, but why not more prominently? Jeff Allen On 28/05/2017 21:45, James Mudd wrote: > Just a few comments from my point of view. > > I think moving to a Github based workflow will help to attract more > contributors to Jython. I just think more people are familiar with the > workflow, so it's less effort to get involved, even minor things like > having to sign up to bugs.jython.org <http://bugs.jython.org> might > put people off. Having said that I really hope more people get > involved. I have really enjoyed putting some work into Jython, and > have got to investigate some interesting bugs which has been really > fun. I think its a unique kind of project which is really interesting > to work on, and all the other contributors seem to be really friendly > and helpful. I hope to keep contributing in the future when time allows. > > Also thanks to Stefan for the comments, and the great discussion on > many of the bugs fixed over the last few months, as well as merging > many of my suggested patches. > > Looking forward to seeing the RC2, and hopefully soon after the final > release. > > James > > On 28 May 2017 at 19:11, Stefan Richthofer <Ste...@gm... > <mailto:Ste...@gm...>> wrote: > > > Agreed that getting on github will not be the most minor fix > > It occurred to me that this change actually aligns with our focus > shift to Jython 3. Maybe we can benefit from this by setting up > the new workflow only for Jython 3. Then it would be kind of a > reboot rather than a (potentially painful) migration. It would > naturaly sort out Jython 3 stuff from Jython 2 stuff. (We could > even consider to track Jython 3 issues on github and continue bjo > just for Jython 2.) Think about it. > > I also felt it was important to highlight Stefan's contribution to helping finalize 2.7.1 > > It's a great honor for me to be mentioned for this. Thank you very > much! > Looking at ACKNOWLEDGEMENTS I found that the file does not > explicitly display who is actually core-developing Jython right > now. Jeff, Jim, Darjus and Frank who are putting a lot of work > into Jython (or did so in the last years) are mentioned randomly > between all contributors, including persons with really minimal > contributions (don't get me wrong - every contribution is very > valuable!). While this is a very modest attitude I think the > (active) core-dev team should be explicitly named somewhere at the > beginning of the file, not lastly because users might need this > info to assess who to ask. Also - maybe I overlooked it - it is > nowhere stated that Frank is the project lead. This should be made > clear IMO. In case we decided to add such a section I'd suggest to > also mention James Mudd, at least for this release, because he > spent significantly more work on Jython than the average contributor. > > I'll get the soft release together this weekend. If there are no troubles, I'll get the hard RC2 out next > week. > > Looking forward to it! Thanks a lot. > > Best regards > -Stefan > *Gesendet:* Samstag, 27. Mai 2017 um 20:43 Uhr > *Von:* "fwi...@gm... <mailto:fwi...@gm...>" > <fwi...@gm... <mailto:fwi...@gm...>> > *An:* "Jim Baker" <jim...@py... <mailto:jim...@py...>> > *Cc:* "Jython Developers" <jyt...@li... > <mailto:jyt...@li...>> > *Betreff:* Re: [Jython-dev] 2.7.1rc, to infinity and beyond! > Great news, and amazing work everyone! I'll get the soft release > together this weekend. If there are no troubles, I'll get the hard > RC2 out next week. > On May 27, 2017 10:46, "Jim Baker" <jim...@py... > <mailto:jim...@py...>> wrote: > > Updated README to state RC2, plus fixed the typo. Thanks for > the feedback! > Agreed that getting on github will not be the most minor fix > (!), but it will be worth the effort. I do like Mercurial, and > very much appreciate the Hg team's help in moving Jython to > hg.python.org <http://hg.python.org> from Subversion. > Nonetheless, we found out in using Mercurial for the last 5 or > so years for Jython development that it didn't match our > development processes. It's both time to move on, and join > CPython upstream in its dev processes. > On Sat, May 27, 2017 at 5:07 AM, Adam Burke > <ada...@gm... <mailto:ada...@gm...>> wrote: > > I know I'm a lurker and not an active dev, but I'd prefer > the rc2 name as well, fwiw. > Cheers > Adam > On 27 May 2017 at 15:33, Jeff Allen <ja...@fa... > <mailto:ja...@fa...>> wrote: > > Excellent news! A lot has gone on between 2.7.0 and > 2.7.1. it's good to find we've all feel "done"at the > same time :) > > Small typo in your front page: "many others to thanks". > > I have a weak preference for calling it RC2 given > there was change after RC1. I think RC1 still > identifies a release, even if it was announced softly, > and what we have now is different. > > There's a bit more to cutting over to Git than > declaring it so. I've been watching CPython do this > with the corner of one eye. We will have both > bugs.jython.org <http://bugs.jython.org> and Git pull > requests for a while ... essentially forever. There > was some integration work (which we should steal, but > that depends, I suspect, on upgrading the tracker) and > conventions for how to refer to one from the other. It > was tough at points because of disagreement on how it > were best done, but we can just go along with their > conclusion. And s/bpo/bjo/. > > Jeff Allen > > On 27/05/2017 01:12, Jim Baker wrote: > > Agreed. It's time for putting this release > candidate out! I'm also glad about the timing, > because this mean Stefan has a great base to build > this summer's work on JyNI. I believe it's > technically RC1 still because the last RC was a > soft release, but Frank knows those specifics. > > I just ran the "yolk smoke test" from > http://bugs.jython.org/issue2570 > <http://bugs.jython.org/issue2570> > <http://bugs.jython.org/issue2570 > <http://bugs.jython.org/issue2570>> one last time, > just to make sure. Everything looks great! > > After this we can look into: > > 1. Finally get jython.org <http://jython.org> > <http://jython.org> revamped. I suggest the > simplicity — and modern look — of GitHub pages, > where we can host and then point jython.org > <http://jython.org> <http://jython.org> accordingly. > 2. Switch to the Gradle build that Darjus has been > working on > 3. Cut over to https://github.com/jython/jython > <https://github.com/jython/jython> with rewritten > history that removes extlib jars for a subsequent > release of 2.7.x, where x > 1 (maybe it's 12 for > the next release, but we can decide later). > > Lastly, I also felt it was important to highlight > Stefan's contribution to helping finalize 2.7.1, > as well as our appreciation to Google for > supporting him this summer for the Google Summer > of Code. First win for GSOC 2017 in other words. > Duly noted as of > https://hg.python.org/jython/rev/ab5434be88aa > <https://hg.python.org/jython/rev/ab5434be88aa> > > - Jim > > > > On May 26, 2017 7:24 PM, "Stefan Richthofer" > <Ste...@gm... > <mailto:Ste...@gm...> > <mailto:Ste...@gm... > <mailto:Ste...@gm...>>> wrote: > > > You can apply these updates to extlibs > Done as of > https://hg.python.org/jython/rev/f6b3ddbc1df8 > <https://hg.python.org/jython/rev/f6b3ddbc1df8> > <https://hg.python.org/jython/rev/f6b3ddbc1df8 > <https://hg.python.org/jython/rev/f6b3ddbc1df8>>. > From my point of view we can launch Jython > 2.7.1-RC2 now. > - no open PRs on github left > - no release blockers left apparently except #2487 > - all updates done as far as possible (python > std-lib will be next > challenge on this front) > So, I'd suggest everybody pushes last-minute > work and Frank hits > the release-button... :-) > What do you think? > Cheers! > -Stefan > > <snip> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the > world's most > engaging tech sites, Slashdot.org! > http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's > most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! > http://sdm.link/slashdot_______________________________________________ > <http://sdm.link/slashdot_______________________________________________> > Jython-dev mailing list Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X