Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Jim Baker <jim.baker@py...>]

On Sat, Jun 24, 2017 at 2:33 AM, Jeff Allen <ja.py@...> wrote:

> Improving our documentation and what is prominent on the website is a good
> idea. Explaining our work accurately in an obvious place will do a lot for
> its usefulness to others and ease contribution.
>
> For example, as I created the simple Eclipse project to answer
> https://github.com/jythontools/jython/issues/78, a user struggling simply
> to get started, I thought that it ought to be on the wiki or somewhere. And
> we never pitched in with Frank's conversion of the Python documentation
> that describes with apparent authority things Jython doesn't do at all.
>
> +1 for using a Github repo. Also, a separate one for a dev guide. The
> CPython dev-guide was the first to migrate, wasn't it?


Indeed, the Jython dev guide currently can be found here:
https://hg.python.org/jython-docs/devguide/ - it should be moved over to
GitHub. Given history from CPython before it was forked, and the chance to
merge forward some of their updates, it's probably best to keep as a
separate repo.


> If we have those two on Github, can we give up the Wiki?
>

+1, no more wiki. We move the content over, and kill. The PR process is
just about as light, and it doesn't have the current problems in the wiki.


> I'd like to help with this, but in the immediate future I'm committed to
> other things -- not for an entire summer of code, you understand, but for
> the next three weeks at least.


It's not a problem! We always have varying availability, especially with
this project. But this flexibility is why I personally can find it easy to
continue to contribute, as I have time.


> So I can only recommend for 1/7 doing things that are least work, like
> linking the CPython 2.7 docs with an appropriate caveat. At least that
> sends a good message about conformance!
>

Any process should be about a simple workflow that's easy to contribute to.
We can then make it better.


> Longer term, I wonder if we can have a kind of filtered re-use, parallel
> to the way we treat the standard library? And the same with the dev guide?
>

Sounds like the right approach. There might be a way to be more systematic
here in how we patch, but the stdlib experience is reasonably light and
easy to work with.


>
> As for tools,  I've used the Maven Sphinx plug-in successfully (and it's
> nice that it depends on Jython).


Interesting detail! Might be the right approach in the future, depending on
our CI system.


> Also using CPython & Sphinx, I have published successfully through
> readthedocs.


I have had decent experience with RTD as well.


> I tried Github pages with Sphinx, but it ended up a mess: ISTR one is
> committing material generated from one branch into an alternate branch.
> Maybe it has got slicker, or maybe I was doing it wrong. Still, it makes me
> a bit wary about diving down that route (and requesting "PSF admins update
> DNS to point jython.org <http://jython.org>; accordingly") rather than
> just linking it from an old-school home page where it is now.
>

I see jython.github.io as just one possible way to render static content,
that is then built by some other tooling against the doc repo, but the more
important thing is just using Sphinx + RST. Everything else in this
rendering pipeline we can readily change.


> ANTLR & StringTemplate just have documentation in the repo that Github
> renders directly, but I found Github markdown insufficient when I tried it
> for each of the jobs I refer to.
>

This is the most common approach, and works for many projects, but given
that RST is the standard for Python docs itself, plus used by the Jython
book, we should stick to RST.

In my other work, I generally prefer Markdown otherwise, especially given
its superior Github browsing integration. I also like being able to readily
embed Latex into Markdown using Pandoc tools, but a separate conversation
altogether. Anyway, it's not possible to have everything!


> I don't know the Travis plug-in. One needs to be able to generate the
> documentation locally, of course. If Travis does so much for us, will we be
> able to check work without opening a PR?
>

Regardless it should still be possible to build without a PR or the CI
itself, just by invoking Sphinx.

Having it on the PR (if possible, RTD doesn't currently support,
https://github.com/rtfd/readthedocs.org/issues/1340) will it make possible
to view changes without having to do this local checkout, which is nicer
workflow IMHO for initial review. So that's the biggest argument for Travis
I think at this time. But first, let's see if it's even workable, and if
not, we can just use RTD.

- Jim

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Jeff Allen <ja.py@fa...>]

Improving our documentation and what is prominent on the website is a 
good idea. Explaining our work accurately in an obvious place will do a 
lot for its usefulness to others and ease contribution.

For example, as I created the simple Eclipse project to answer 
https://github.com/jythontools/jython/issues/78, a user struggling 
simply to get started, I thought that it ought to be on the wiki or 
somewhere. And we never pitched in with Frank's conversion of the Python 
documentation that describes with apparent authority things Jython 
doesn't do at all.

+1 for using a Github repo. Also, a separate one for a dev guide. The 
CPython dev-guide was the first to migrate, wasn't it? If we have those 
two on Github, can we give up the Wiki?

I'd like to help with this, but in the immediate future I'm committed to 
other things -- not for an entire summer of code, you understand, but 
for the next three weeks at least. So I can only recommend for 1/7 doing 
things that are least work, like linking the CPython 2.7 docs with an 
appropriate caveat. At least that sends a good message about conformance!

Longer term, I wonder if we can have a kind of filtered re-use, parallel 
to the way we treat the standard library? And the same with the dev guide?

As for tools,  I've used the Maven Sphinx plug-in successfully (and it's 
nice that it depends on Jython). Also using CPython & Sphinx, I have 
published successfully through readthedocs. I tried Github pages with 
Sphinx, but it ended up a mess: ISTR one is committing material 
generated from one branch into an alternate branch. Maybe it has got 
slicker, or maybe I was doing it wrong. Still, it makes me a bit wary 
about diving down that route (and requesting "PSF admins update DNS to 
point jython.org <http://jython.org>; accordingly") rather than just 
linking it from an old-school home page where it is now.

ANTLR & StringTemplate just have documentation in the repo that Github 
renders directly, but I found Github markdown insufficient when I tried 
it for each of the jobs I refer to.

I don't know the Travis plug-in. One needs to be able to generate the 
documentation locally, of course. If Travis does so much for us, will we 
be able to check work without opening a PR?

Jeff


On 23/06/2017 01:16, Stefan Richthofer wrote:
> +1 on the docs front. Also for moving from news-centric perspective to 
> general setup/usage.
> So many requests here and on IRC are due to old doc and old homepage.
> Unfortunately I cannot contribute to this effort in near future, 
> certainly not during GSoC period. But thanks for kicking this off!
> >> I'm sure there's other material we can use, drawing from the wiki, 
> the book, and other sources.
> Sooner or later I'd like to add the examples from this paper: 
> https://arxiv.org/pdf/1607.00825.pdf
> Note that the tkinter-from-Java example is more about Jython/Java 
> integration via Py.newJ method family, which makes
> access of Python API from Java more convenient. Stuff involving JyNI 
> would be labeled experimental.
> Maybe I will also find a JyNI-independent Py.newJ example.
> -Stefan
> *Gesendet:* Donnerstag, 22. Juni 2017 um 22:41 Uhr
> *Von:* "Jim Baker" <jim.baker@...>
> *An:* "Jeff Allen" <ja.py@...>
> *Cc:* "Jython Developers" <jython-dev@...>
> *Betreff:* Re: [Jython-dev] Jython 2.7.1 rc3 soft release
> So far everything is working well for me on OSX and Ubuntu with RC3, 
> as expected. We have also had no new bug reports against RC3. So 
> everything is looking good for a July 1 release.
> At this point, I think it's more about us updating our docs. I was on 
> vacation for the last few days, but on the plane back yesterday I 
> started to work on what we might want to do to update from our current 
> site.
> The current repo for the jython.org <http://jython.org>; website is at 
> https://hg.python.org/jython-docs/website/, with the build process 
> described by 
> https://hg.python.org/jython-docs/website/file/tip/README.txt Note 
> that the bulk of the repo is a pushed version of the build itself; of 
> that, it's mostly the Python 2.6 docs IIRC.
> Most likely what we should do is use travis-ci to build our docs from 
> a new github repo, using content in RST that Sphinx can build, then 
> push onto github pages for jython.github.io <http://jython.github.io>;; 
> we can have the PSF admins update DNS to point jython.org 
> <http://jython.org>; accordingly. 
> https://github.com/Syntaf/travis-sphinx looks promising in terms of 
> some specific setup aspects. For now, I would just link against the 
> python.org <http://python.org>; 2.7 docs, vs trying to maintain our own 
> copy (which is not current against either Jython 2.5 or 2.7 regardless).
> As for front page content, I would emphasize news less than the 
> current Jython site, and more about how Jython can and should be used. 
> This is similar to what is done for python.org <http://python.org>; 
> itself. I have content from my Jython talk from PyCon from 2015 that 
> can be repurposed here, as well as the article I co-authored with Josh 
> Juneau for Java Magazine. I'm sure there's other material we can use, 
> drawing from the wiki, the book, and other sources.
> Ideally we can complete this all by July 1, by keeping it focused and 
> again reusing what we already have. Most importantly this leaves us in 
> place with a workflow that can help keep the site more up-to-date 
> through standard PRs than what we have now.
> Any thoughts?
> - Jim
> On Thu, Jun 22, 2017 at 12:48 PM, Jeff Allen <ja.py@... 
> <mailto:ja.py@...>> wrote:
>
>     I confirm essentially the same results for user 用户名  with Chinese
>     localisation. (Jython works fine, but pip only if you're ASCII.)
>
>     Jeff
>
>
>     On 19/06/2017 08:15, Jeff Allen wrote:
>
>         I tried this on my user account "Épreuve" to check basic
>         non-ascii handling on Windows. The result is not totally
>         clean, but I would say we're still ok.
>
>         I used the standard installer, but to a directory within
>         C:\Users\Épreuve\... as non-ascii paths to the installation
>         directory were an issue. And I ran the regression tests with -e.
>
>         I get the test failures noted in
>         http://bugs.jython.org/issue2594 and
>         http://bugs.jython.org/issue2308, which involve things missing
>         from the environment we deliver to users, or they are faults
>         in the tests that expect something different.
>
>         I get two failures (in test_socket and test_urllib2_localnet)
>         that are to do with my ISP's ever more aggressive approach to
>         mis-typed URLs. This is a change for the worse. Would you
>         believe that on my machine I can actually ping
>         non.existent.server and get a round-trip time of 20ms? Thanks
>         guys.
>
>         And I get showers of netty errors again. :( But not so as the
>         test fails.
>
>         Then I tried pip, which doesn't like non-ascii paths much. pip
>         install yolk (failed) and then after pip uninstall yolk,  I
>         tried jython -m pip install yolk (failed). Both failed trying
>         to encode a path to ascii (to write to file, I think), towards
>         the end of the process, when running setup_yolk.py (I think).
>         To my surprise, jython -m pip install sphinx ran to completion
>         (a surprise since it brings so many subsidiary packages it
>         seemed sure to fail). So I suspect the yolk failure, although
>         it occurs down in the support libraries, actually stems from
>         the use of default encoding to write FS-encoded data,
>         traceable back to yolk itself.
>
>         I haven't tried this with Chinese localisation yet, as it
>         takes a bit more to set up.
>
>         Bottom line: our bit works, but doesn't make up for others'
>         shortcomings. We can all feel justly satisfied.
>
>         Jeff
>
>
>
>         On 17/06/2017 17:48, fwierzbicki@...
>         <mailto:fwierzbicki@...> wrote:
>
>             Hi all,
>
>             I've put together a soft release of 2.7.1 rc2.
>
>             Please test! As soon as I get a couple of sanity checks,
>             I'll finalize
>             the RC and do a real announcement.
>
>             The releases:
>
>             installer:
>             https://oss.sonatype.org/content/repositories/orgpython-1067/org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar
>
>             standalone:
>             https://oss.sonatype.org/content/repositories/orgpython-1068/org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar
>
>             The parent directories of each of the above have the
>             checksums, source
>             jars, javadocs, etc.
>
>             -Frank
>
>             ------------------------------------------------------------------------------
>             Check out the vibrant tech community on one of the world's
>             most
>             engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>             _______________________________________________
>             Jython-dev mailing list
>             Jython-dev@...
>             <mailto: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
>         Jython-dev@...
>         <mailto: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
>     Jython-dev@...
>     <mailto: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 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
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev

[Jython-dev] Summary of Jython tracker Issues

[Jython tracker <status@bu...>]

ACTIVITY SUMMARY (2017-06-16 - 2017-06-23)
Jython tracker at http://bugs.jython.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open     302 ( -2)
  closed  2315 ( +2)
  total   2617 ( +0)

Open issues with patches: 28   


Most recent 15 issues with no replies (15)
==========================================

#2591: Unable to execute directory or zip file (test_cmd_line_script)
http://bugs.jython.org/issue2591

#2567: System state lost during JSR-223 initialisation
http://bugs.jython.org/issue2567

#2562: Windows: OSError: unlink(): an unknown error occurred
http://bugs.jython.org/issue2562

#2543: broken links for mailing list website
http://bugs.jython.org/issue2543

#2540: settrace doesn't notice "with" statements
http://bugs.jython.org/issue2540

#2531: Support SNI for SSL/TLS server sockets
http://bugs.jython.org/issue2531

#2525: Jython incorrectly buffers file pipe output with Subprocess(co
http://bugs.jython.org/issue2525

#2520: Jython does NOT support socket.listen(0) for accepting only on
http://bugs.jython.org/issue2520

#2512: Values in built-in modules's __dict__ are “<reflected field 
http://bugs.jython.org/issue2512

#2510: TypeError when monkey-patching time.time with an unbound funct
http://bugs.jython.org/issue2510

#2507: Run "invokeFunction" in a thread does not inherit the "ScriptC
http://bugs.jython.org/issue2507

#2494: Support for pydoc_data
http://bugs.jython.org/issue2494

#2484: Codec encodings can exhaust permgen
http://bugs.jython.org/issue2484

#2482: Publish U.S. ECCN for Jython
http://bugs.jython.org/issue2482

#2422: test_classpathimporter fauls on Linux
http://bugs.jython.org/issue2422



Most recent 15 issues waiting for review (15)
=============================================

#2566: inspect does not recognize code objects from bytecode files
http://bugs.jython.org/issue2566

#2545: help() does not work on Java-implemented modules
http://bugs.jython.org/issue2545

#2429: cStringIO does not work with mutable objects implementing the 
http://bugs.jython.org/issue2429

#2367: Jython ignores custom __eq__ when hashing dict subclasses
http://bugs.jython.org/issue2367

#2330: full-build fails to copy CPython License
http://bugs.jython.org/issue2330

#2230: Jython evaluation blocks under heavy load with high multi-core
http://bugs.jython.org/issue2230

#2143: site-packages support in standalone jar
http://bugs.jython.org/issue2143

#2142: Set Thread classloader when entering Jython context
http://bugs.jython.org/issue2142

#2121: Jython jar on Maven central embeds other third party libraries
http://bugs.jython.org/issue2121

#2077: marshal doesn't raise error when fed unmarshalable object
http://bugs.jython.org/issue2077

#1925: Support loading java.sql.Drivers that aren't on the boot class
http://bugs.jython.org/issue1925

#1917: No ctypes.c_char
http://bugs.jython.org/issue1917

#1866: Parser does not have mismatch token error messages caught by B
http://bugs.jython.org/issue1866

#1842: Add IBM i support to Jython
http://bugs.jython.org/issue1842

#1796: Jython doesn't support jar dir with colon's in it
http://bugs.jython.org/issue1796

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Stefan Richthofer <Stefan.Richthofer@gm...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>+1 on the docs front. Also for moving from news-centric perspective to general setup/usage.</div>

<div>So many requests here and on IRC are due to old doc and old homepage.</div>

<div>Unfortunately I cannot contribute to this effort in near future, certainly not during GSoC period. But thanks for kicking this off!</div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>&gt;&gt; I&#39;m sure there&#39;s other material we can use, drawing from the wiki, the book, and other sources.</div>

<div>&nbsp;</div>

<div>Sooner or later I&#39;d like to add the examples from this paper: https://arxiv.org/pdf/1607.00825.pdf</div>;

<div>Note that the tkinter-from-Java example is more about Jython/Java integration via Py.newJ method family, which makes</div>

<div>access of Python API from Java more convenient. Stuff involving JyNI would be labeled experimental.</div>

<div>Maybe I will also find a JyNI-independent Py.newJ example.</div>

<div>&nbsp;</div>

<div>-Stefan</div>

<div>&nbsp;</div>

<div>&nbsp;
<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>&nbsp;Donnerstag, 22. Juni 2017 um 22:41 Uhr<br/>
<b>Von:</b>&nbsp;&quot;Jim Baker&quot; &lt;jim.baker@...&gt;<br/>
<b>An:</b>&nbsp;&quot;Jeff Allen&quot; &lt;ja.py@...&gt;<br/>
<b>Cc:</b>&nbsp;&quot;Jython Developers&quot; &lt;jython-dev@...&gt;<br/>
<b>Betreff:</b>&nbsp;Re: [Jython-dev] Jython 2.7.1 rc3 soft release</div>

<div name="quoted-content">
<div>So far everything is working well for me on OSX and Ubuntu with RC3, as expected. We have also had no new bug reports against RC3. So everything is looking good for a July 1 release.
<div>&nbsp;</div>

<div>At this point, I think it&#39;s more about us updating our docs. I was on vacation for the last few days, but on the plane back yesterday I started to work on what we might want to do to update from our current site.</div>

<div>&nbsp;</div>

<div>The current repo for the <a href="http://jython.org"; target="_blank">jython.org</a> website is at <a href="https://hg.python.org/jython-docs/website/"; target="_blank">https://hg.python.org/jython-docs/website/</a>;, with the build process described by&nbsp;<a href="https://hg.python.org/jython-docs/website/file/tip/README.txt"; target="_blank">https://hg.python.org/jython-docs/website/file/tip/README.txt</a>; Note that the bulk of the repo is a pushed version of the build itself; of that, it&#39;s mostly the Python 2.6 docs IIRC.</div>

<div>&nbsp;</div>

<div>Most likely what we should do is use travis-ci to build our docs from a new github repo, using content in RST that Sphinx can build, then push onto github pages for <a href="http://jython.github.io"; target="_blank">jython.github.io</a>; we can have the PSF admins update DNS to point <a href="http://jython.org"; target="_blank">jython.org</a> accordingly.&nbsp;<a href="https://github.com/Syntaf/travis-sphinx"; target="_blank">https://github.com/Syntaf/travis-sphinx</a>; looks promising in terms of some specific setup aspects. For now, I would just link against the <a href="http://python.org"; target="_blank">python.org</a> 2.7 docs, vs trying to maintain our own copy (which is not current against either Jython 2.5 or 2.7 regardless).</div>

<div>&nbsp;</div>

<div>As for front page content, I would emphasize news less than the current Jython site, and more about how Jython can and should be used. This is similar to what is done for <a href="http://python.org"; target="_blank">python.org</a> itself. I have content from my Jython talk from PyCon from 2015 that can be repurposed here, as well as the article I co-authored with Josh Juneau for Java Magazine. I&#39;m sure there&#39;s other material we can use, drawing from the wiki, the book, and other sources.</div>

<div>&nbsp;</div>

<div>Ideally we can complete this all by July 1, by keeping it focused and again reusing what we already have. Most importantly this leaves us in place with a workflow that can help keep the site more up-to-date through standard PRs than what we have now.</div>

<div>&nbsp;</div>

<div>Any thoughts?</div>

<div>&nbsp;</div>

<div>- Jim</div>

<div class="gmail_extra">&nbsp;
<div class="gmail_quote">On Thu, Jun 22, 2017 at 12:48 PM, Jeff Allen <span>&lt;<a href="mailto:ja.py@..." onclick="parent.window.location.href=&#39;ja.py@...&#39;; return false;" target="_blank">ja.py@...</a>&gt;</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 confirm essentially the same results for user &#29992;&#25143;&#21517;&nbsp; with Chinese localisation. (Jython works fine, but pip only if you&#39;re ASCII.)<br/>
<br/>
<span class="m_7524362446823465177HOEnZb"><font color="#888888">Jeff</font></span>

<div class="m_7524362446823465177HOEnZb">
<div class="m_7524362446823465177h5"><br/>
<br/>
On 19/06/2017 08:15, Jeff Allen 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 tried this on my user account &quot;&Eacute;preuve&quot; to check basic non-ascii handling on Windows. The result is not totally clean, but I would say we&#39;re still ok.<br/>
<br/>
I used the standard installer, but to a directory within C:&#92;Users&#92;&Eacute;preuve&#92;... as non-ascii paths to the installation directory were an issue. And I ran the regression tests with -e.<br/>
<br/>
I get the test failures noted in <a href="http://bugs.jython.org/issue2594"; target="_blank">http://bugs.jython.org/issue2594</a>; and <a href="http://bugs.jython.org/issue2308"; target="_blank">http://bugs.jython.org/issue2308</a>;, which involve things missing from the environment we deliver to users, or they are faults in the tests that expect something different.<br/>
<br/>
I get two failures (in test_socket and test_urllib2_localnet) that are to do with my ISP&#39;s ever more aggressive approach to mis-typed URLs. This is a change for the worse. Would you believe that on my machine I can actually ping non.existent.server and get a round-trip time of 20ms? Thanks guys.<br/>
<br/>
And I get showers of netty errors again. :( But not so as the test fails.<br/>
<br/>
Then I tried pip, which doesn&#39;t like non-ascii paths much. pip install yolk (failed) and then after pip uninstall yolk,&nbsp; I tried jython -m pip install yolk (failed). Both failed trying to encode a path to ascii (to write to file, I think), towards the end of the process, when running setup_yolk.py (I think). To my surprise, jython -m pip install sphinx ran to completion (a surprise since it brings so many subsidiary packages it seemed sure to fail). So I suspect the yolk failure, although it occurs down in the support libraries, actually stems from the use of default encoding to write FS-encoded data, traceable back to yolk itself.<br/>
<br/>
I haven&#39;t tried this with Chinese localisation yet, as it takes a bit more to set up.<br/>
<br/>
Bottom line: our bit works, but doesn&#39;t make up for others&#39; shortcomings. We can all feel justly satisfied.<br/>
<br/>
Jeff<br/>
<br/>
<br/>
<br/>
On 17/06/2017 17:48, <a href="mailto:fwierzbicki@..." onclick="parent.window.location.href=&#39;fwierzbicki@...&#39;; return false;" target="_blank">fwierzbicki@...</a> 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;">Hi all,<br/>
<br/>
I&#39;ve put together a soft release of 2.7.1 rc2.<br/>
<br/>
Please test! As soon as I get a couple of sanity checks, I&#39;ll finalize<br/>
the RC and do a real announcement.<br/>
<br/>
The releases:<br/>
<br/>
installer: <a href="https://oss.sonatype.org/content/repositories/orgpython-1067/org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar"; target="_blank">https://oss.sonatype.org/content/repositories/orgpython-1067/org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar</a><br/>;
<br/>
standalone: <a href="https://oss.sonatype.org/content/repositories/orgpython-1068/org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar"; target="_blank">https://oss.sonatype.org/content/repositories/orgpython-1068/org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar</a><br/>;
<br/>
The parent directories of each of the above have the checksums, source<br/>
jars, javadocs, etc.<br/>
<br/>
-Frank<br/>
<br/>
------------------------------------------------------------------------------<br/>
Check out the vibrant tech community on one of the world&#39;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:Jython-dev@..." onclick="parent.window.location.href=&#39;Jython-dev@...&#39;; return false;" target="_blank">Jython-dev@...</a><br/>
<a href="https://lists.sourceforge.net/lists/listinfo/jython-dev"; target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a><br/>;
&nbsp;</blockquote>
<br/>
<br/>
------------------------------------------------------------------------------<br/>
Check out the vibrant tech community on one of the world&#39;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:Jython-dev@..." onclick="parent.window.location.href=&#39;Jython-dev@...&#39;; return false;" target="_blank">Jython-dev@...</a><br/>
<a href="https://lists.sourceforge.net/lists/listinfo/jython-dev"; target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></blockquote>;
<br/>
<br/>
------------------------------------------------------------------------------<br/>
Check out the vibrant tech community on one of the world&#39;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:Jython-dev@..." onclick="parent.window.location.href=&#39;Jython-dev@...&#39;; return false;" target="_blank">Jython-dev@...</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>
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world&#39;s most engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot_______________________________________________"; target="_blank">http://sdm.link/slashdot_______________________________________________</a>; Jython-dev mailing list Jython-dev@... <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>

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Jim Baker <jim.baker@py...>]

So far everything is working well for me on OSX and Ubuntu with RC3, as
expected. We have also had no new bug reports against RC3. So everything is
looking good for a July 1 release.

At this point, I think it's more about us updating our docs. I was on
vacation for the last few days, but on the plane back yesterday I started
to work on what we might want to do to update from our current site.

The current repo for the jython.org website is at
https://hg.python.org/jython-docs/website/, with the build process
described by https://hg.python.org/jython-docs/website/file/tip/README.txt
Note that the bulk of the repo is a pushed version of the build itself; of
that, it's mostly the Python 2.6 docs IIRC.

Most likely what we should do is use travis-ci to build our docs from a new
github repo, using content in RST that Sphinx can build, then push onto
github pages for jython.github.io; we can have the PSF admins update DNS to
point jython.org accordingly. https://github.com/Syntaf/travis-sphinx looks
promising in terms of some specific setup aspects. For now, I would just
link against the python.org 2.7 docs, vs trying to maintain our own copy
(which is not current against either Jython 2.5 or 2.7 regardless).

As for front page content, I would emphasize news less than the current
Jython site, and more about how Jython can and should be used. This is
similar to what is done for python.org itself. I have content from my
Jython talk from PyCon from 2015 that can be repurposed here, as well as
the article I co-authored with Josh Juneau for Java Magazine. I'm sure
there's other material we can use, drawing from the wiki, the book, and
other sources.

Ideally we can complete this all by July 1, by keeping it focused and again
reusing what we already have. Most importantly this leaves us in place with
a workflow that can help keep the site more up-to-date through standard PRs
than what we have now.

Any thoughts?

- Jim

On Thu, Jun 22, 2017 at 12:48 PM, Jeff Allen <ja.py@...> wrote:

> I confirm essentially the same results for user 用户名  with Chinese
> localisation. (Jython works fine, but pip only if you're ASCII.)
>
> Jeff
>
>
> On 19/06/2017 08:15, Jeff Allen wrote:
>
>> I tried this on my user account "Épreuve" to check basic non-ascii
>> handling on Windows. The result is not totally clean, but I would say we're
>> still ok.
>>
>> I used the standard installer, but to a directory within
>> C:\Users\Épreuve\... as non-ascii paths to the installation directory were
>> an issue. And I ran the regression tests with -e.
>>
>> I get the test failures noted in http://bugs.jython.org/issue2594 and
>> http://bugs.jython.org/issue2308, which involve things missing from the
>> environment we deliver to users, or they are faults in the tests that
>> expect something different.
>>
>> I get two failures (in test_socket and test_urllib2_localnet) that are to
>> do with my ISP's ever more aggressive approach to mis-typed URLs. This is a
>> change for the worse. Would you believe that on my machine I can actually
>> ping non.existent.server and get a round-trip time of 20ms? Thanks guys.
>>
>> And I get showers of netty errors again. :( But not so as the test fails.
>>
>> Then I tried pip, which doesn't like non-ascii paths much. pip install
>> yolk (failed) and then after pip uninstall yolk,  I tried jython -m pip
>> install yolk (failed). Both failed trying to encode a path to ascii (to
>> write to file, I think), towards the end of the process, when running
>> setup_yolk.py (I think). To my surprise, jython -m pip install sphinx ran
>> to completion (a surprise since it brings so many subsidiary packages it
>> seemed sure to fail). So I suspect the yolk failure, although it occurs
>> down in the support libraries, actually stems from the use of default
>> encoding to write FS-encoded data, traceable back to yolk itself.
>>
>> I haven't tried this with Chinese localisation yet, as it takes a bit
>> more to set up.
>>
>> Bottom line: our bit works, but doesn't make up for others' shortcomings.
>> We can all feel justly satisfied.
>>
>> Jeff
>>
>>
>>
>> On 17/06/2017 17:48, fwierzbicki@... wrote:
>>
>>> Hi all,
>>>
>>> I've put together a soft release of 2.7.1 rc2.
>>>
>>> Please test! As soon as I get a couple of sanity checks, I'll finalize
>>> the RC and do a real announcement.
>>>
>>> The releases:
>>>
>>> installer: https://oss.sonatype.org/content/repositories/orgpython-1067
>>> /org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar
>>>
>>> standalone: https://oss.sonatype.org/content/repositories/orgpython-1068
>>> /org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar
>>>
>>> The parent directories of each of the above have the checksums, source
>>> jars, javadocs, etc.
>>>
>>> -Frank
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Jython-dev mailing list
>>> Jython-dev@...
>>> https://lists.sourceforge.net/lists/listinfo/jython-dev
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Jython-dev mailing list
>> Jython-dev@...
>> https://lists.sourceforge.net/lists/listinfo/jython-dev
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Jeff Allen <ja.py@fa...>]

I confirm essentially the same results for user 用户名  with Chinese 
localisation. (Jython works fine, but pip only if you're ASCII.)

Jeff

On 19/06/2017 08:15, Jeff Allen wrote:
> I tried this on my user account "Épreuve" to check basic non-ascii 
> handling on Windows. The result is not totally clean, but I would say 
> we're still ok.
>
> I used the standard installer, but to a directory within 
> C:\Users\Épreuve\... as non-ascii paths to the installation directory 
> were an issue. And I ran the regression tests with -e.
>
> I get the test failures noted in http://bugs.jython.org/issue2594 and 
> http://bugs.jython.org/issue2308, which involve things missing from 
> the environment we deliver to users, or they are faults in the tests 
> that expect something different.
>
> I get two failures (in test_socket and test_urllib2_localnet) that are 
> to do with my ISP's ever more aggressive approach to mis-typed URLs. 
> This is a change for the worse. Would you believe that on my machine I 
> can actually ping non.existent.server and get a round-trip time of 
> 20ms? Thanks guys.
>
> And I get showers of netty errors again. :( But not so as the test fails.
>
> Then I tried pip, which doesn't like non-ascii paths much. pip install 
> yolk (failed) and then after pip uninstall yolk,  I tried jython -m 
> pip install yolk (failed). Both failed trying to encode a path to 
> ascii (to write to file, I think), towards the end of the process, 
> when running setup_yolk.py (I think). To my surprise, jython -m pip 
> install sphinx ran to completion (a surprise since it brings so many 
> subsidiary packages it seemed sure to fail). So I suspect the yolk 
> failure, although it occurs down in the support libraries, actually 
> stems from the use of default encoding to write FS-encoded data, 
> traceable back to yolk itself.
>
> I haven't tried this with Chinese localisation yet, as it takes a bit 
> more to set up.
>
> Bottom line: our bit works, but doesn't make up for others' 
> shortcomings. We can all feel justly satisfied.
>
> Jeff
>
>
>
> On 17/06/2017 17:48, fwierzbicki@... wrote:
>> Hi all,
>>
>> I've put together a soft release of 2.7.1 rc2.
>>
>> Please test! As soon as I get a couple of sanity checks, I'll finalize
>> the RC and do a real announcement.
>>
>> The releases:
>>
>> installer: 
>> https://oss.sonatype.org/content/repositories/orgpython-1067/org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar
>>
>> standalone: 
>> https://oss.sonatype.org/content/repositories/orgpython-1068/org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar
>>
>> The parent directories of each of the above have the checksums, source
>> jars, javadocs, etc.
>>
>> -Frank
>>
>> ------------------------------------------------------------------------------ 
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Jython-dev mailing list
>> Jython-dev@...
>> https://lists.sourceforge.net/lists/listinfo/jython-dev
>>
>
>
> ------------------------------------------------------------------------------ 
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev

[Jython-dev] Jython 2.7.1 rc3 released!

[<fwierzbicki@gm...>]

On behalf of the Jython development team, I'm pleased to announce that
Jython 2.7.1 rc3 is released!

Thanks to Amobee for sponsoring my work on Jython, and thanks to the
many contributors to Jython!

Details are here:

http://fwierzbicki.blogspot.com/2017/06/jython-271-release-candidate-3-released.html

-Frank

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Stefan Richthofer <Stefan.Richthofer@gm...>]

Having Jython 2.7.1 release on 2017-7-1 would be awesome! The date is like made for this.
Additionally this release cycle gives us plenty of time to release
2.7.2 on 2027-7-2
and
3.6.0 on 2036-6-0... hmm something wrong here. Should rather be 3006-6-0.. hmmm no.

Best

-Stefan

> Gesendet: Montag, 19. Juni 2017 um 23:51 Uhr
> Von: "fwierzbicki@..." <fwierzbicki@...>
> An: "Jeff Allen" <ja.py@...>
> Cc: "Jython Developers" <jython-dev@...>
> Betreff: Re: [Jython-dev] Jython 2.7.1 rc3 soft release
>
> If no one objects, I'll release rc3 for real tonight. If all goes well
> we'll make it a real release on 7/1 since as Jim was saying it will be
> nice to release 2.7.1 on 7/1 :)
> 
> -Frank
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
> 

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[<fwierzbicki@gm...>]

If no one objects, I'll release rc3 for real tonight. If all goes well
we'll make it a real release on 7/1 since as Jim was saying it will be
nice to release 2.7.1 on 7/1 :)

-Frank

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[Jeff Allen <ja.py@fa...>]

I tried this on my user account "Épreuve" to check basic non-ascii 
handling on Windows. The result is not totally clean, but I would say 
we're still ok.

I used the standard installer, but to a directory within 
C:\Users\Épreuve\... as non-ascii paths to the installation directory 
were an issue. And I ran the regression tests with -e.

I get the test failures noted in http://bugs.jython.org/issue2594 and 
http://bugs.jython.org/issue2308, which involve things missing from the 
environment we deliver to users, or they are faults in the tests that 
expect something different.

I get two failures (in test_socket and test_urllib2_localnet) that are 
to do with my ISP's ever more aggressive approach to mis-typed URLs. 
This is a change for the worse. Would you believe that on my machine I 
can actually ping non.existent.server and get a round-trip time of 20ms? 
Thanks guys.

And I get showers of netty errors again. :( But not so as the test fails.

Then I tried pip, which doesn't like non-ascii paths much. pip install 
yolk (failed) and then after pip uninstall yolk,  I tried jython -m pip 
install yolk (failed). Both failed trying to encode a path to ascii (to 
write to file, I think), towards the end of the process, when running 
setup_yolk.py (I think). To my surprise, jython -m pip install sphinx 
ran to completion (a surprise since it brings so many subsidiary 
packages it seemed sure to fail). So I suspect the yolk failure, 
although it occurs down in the support libraries, actually stems from 
the use of default encoding to write FS-encoded data, traceable back to 
yolk itself.

I haven't tried this with Chinese localisation yet, as it takes a bit 
more to set up.

Bottom line: our bit works, but doesn't make up for others' 
shortcomings. We can all feel justly satisfied.

Jeff



On 17/06/2017 17:48, fwierzbicki@... wrote:
> Hi all,
>
> I've put together a soft release of 2.7.1 rc2.
>
> Please test! As soon as I get a couple of sanity checks, I'll finalize
> the RC and do a real announcement.
>
> The releases:
>
> installer: https://oss.sonatype.org/content/repositories/orgpython-1067/org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar
>
> standalone: https://oss.sonatype.org/content/repositories/orgpython-1068/org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar
>
> The parent directories of each of the above have the checksums, source
> jars, javadocs, etc.
>
> -Frank
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[<fwierzbicki@gm...>]

By the way, a huge thank you to everyone that has worked on
stabilizing the test suite, I haven't seen a single failure in over a
dozen test runs.

-Frank

Re: [Jython-dev] Jython 2.7.1 rc3 soft release

[<fwierzbicki@gm...>]

On Sat, Jun 17, 2017 at 9:48 AM, fwierzbicki@...
<fwierzbicki@...> wrote:
> Hi all,
>
> I've put together a soft release of 2.7.1 rc2.
of course I meant 2.7.1rc3 :)

[Jython-dev] Jython 2.7.1 rc3 soft release

[<fwierzbicki@gm...>]

Hi all,

I've put together a soft release of 2.7.1 rc2.

Please test! As soon as I get a couple of sanity checks, I'll finalize
the RC and do a real announcement.

The releases:

installer: https://oss.sonatype.org/content/repositories/orgpython-1067/org/python/jython-installer/2.7.1-rc3/jython-installer-2.7.1-rc3.jar

standalone: https://oss.sonatype.org/content/repositories/orgpython-1068/org/python/jython-standalone/2.7.1-rc3/jython-standalone-2.7.1-rc3.jar

The parent directories of each of the above have the checksums, source
jars, javadocs, etc.

-Frank

[Jython-dev] Summary of Jython tracker Issues

[Jython tracker <status@bu...>]

ACTIVITY SUMMARY (2017-06-09 - 2017-06-16)
Jython tracker at http://bugs.jython.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open     304 ( -2)
  closed  2313 ( +3)
  total   2617 ( +1)

Open issues with patches: 28   


Issues opened (1)
=================

#2598: Parsing of `from . import something` is incorrect
http://bugs.jython.org/issue2598  opened by jenselme



Most recent 15 issues with no replies (15)
==========================================

#2591: Unable to execute directory or zip file (test_cmd_line_script)
http://bugs.jython.org/issue2591

#2567: System state lost during JSR-223 initialisation
http://bugs.jython.org/issue2567

#2562: Windows: OSError: unlink(): an unknown error occurred
http://bugs.jython.org/issue2562

#2543: broken links for mailing list website
http://bugs.jython.org/issue2543

#2540: settrace doesn't notice "with" statements
http://bugs.jython.org/issue2540

#2531: Support SNI for SSL/TLS server sockets
http://bugs.jython.org/issue2531

#2525: Jython incorrectly buffers file pipe output with Subprocess(co
http://bugs.jython.org/issue2525

#2520: Jython does NOT support socket.listen(0) for accepting only on
http://bugs.jython.org/issue2520

#2512: Values in built-in modules's __dict__ are “<reflected field 
http://bugs.jython.org/issue2512

#2510: TypeError when monkey-patching time.time with an unbound funct
http://bugs.jython.org/issue2510

#2507: Run "invokeFunction" in a thread does not inherit the "ScriptC
http://bugs.jython.org/issue2507

#2494: Support for pydoc_data
http://bugs.jython.org/issue2494

#2484: Codec encodings can exhaust permgen
http://bugs.jython.org/issue2484

#2482: Publish U.S. ECCN for Jython
http://bugs.jython.org/issue2482

#2422: test_classpathimporter fauls on Linux
http://bugs.jython.org/issue2422



Most recent 15 issues waiting for review (15)
=============================================

#2566: inspect does not recognize code objects from bytecode files
http://bugs.jython.org/issue2566

#2545: help() does not work on Java-implemented modules
http://bugs.jython.org/issue2545

#2429: cStringIO does not work with mutable objects implementing the 
http://bugs.jython.org/issue2429

#2367: Jython ignores custom __eq__ when hashing dict subclasses
http://bugs.jython.org/issue2367

#2330: full-build fails to copy CPython License
http://bugs.jython.org/issue2330

#2230: Jython evaluation blocks under heavy load with high multi-core
http://bugs.jython.org/issue2230

#2143: site-packages support in standalone jar
http://bugs.jython.org/issue2143

#2142: Set Thread classloader when entering Jython context
http://bugs.jython.org/issue2142

#2121: Jython jar on Maven central embeds other third party libraries
http://bugs.jython.org/issue2121

#2077: marshal doesn't raise error when fed unmarshalable object
http://bugs.jython.org/issue2077

#1925: Support loading java.sql.Drivers that aren't on the boot class
http://bugs.jython.org/issue1925

#1917: No ctypes.c_char
http://bugs.jython.org/issue1917

#1866: Parser does not have mismatch token error messages caught by B
http://bugs.jython.org/issue1866

#1842: Add IBM i support to Jython
http://bugs.jython.org/issue1842

#1796: Jython doesn't support jar dir with colon's in it
http://bugs.jython.org/issue1796



Top 10 most discussed issues (2)
================================

#2597: PySystemState.sysClosers requires cleanup to prevent memory le
http://bugs.jython.org/issue2597   4 msgs

#2598: Parsing of `from . import something` is incorrect
http://bugs.jython.org/issue2598   3 msgs



Issues closed (1)
=================

#2593: file.write(obj) if obj is not a str or buffer raises j.l.NullP
http://bugs.jython.org/issue2593  closed by jeff.allen

[Jython-dev] JDK 9 EA Build 174 & JDK 8u152 b04 are available on jdk.java.net

[Rory O'Donnell <rory.odonnell@or...>]

Hi Alan,

*JDK 9 Early Access*  build 174  is available at : - jdk.java.net/9/

A summary of all the changes in this build are listed here 
<http://download.java.net/java/jdk9/changes/jdk-9+174.html>;.

Changes which were introduced since the last availability email that may 
be of interest :

  * b172 - JDK-8179014 : JFileChooser with Windows look and feel crashes
    on win 10
  * b173 - JDK-8180582 : the bind to rmiregistry is rejected by
    registryFilter even though registryFilter is set
  * b174 - JDK-8181702  : deprecate for removal the following tool
    modules:jdk.xml.bind and jdk.xml.ws

*JDK 9 Schedule Update*

  * The new GA date for JDK 9 is now set to 2017-09-21 [1]
  * We have updated the OpenJDK JDK 9 project page [2] with the new
    milestones and GA date.


*JDK 8u152 Early Access*  build 04 is available at : - jdk.java.net/8/ 
<http://jdk.java.net/8/>;

A summary of all the changes in this build are listed here 
<http://download.java.net/java/jdk8u152/changes/jdk8u152-b04.html>;.
Information and schedules specific to OpenJDK 8u152 release [3]

Rgds,Rory

[1] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-June/005867.html
[2] http://openjdk.java.net/projects/jdk9/
[3] http://openjdk.java.net/projects/jdk8u/releases/8u152.html

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1

[Jim Baker <jim.baker@py...>]

It looks like we will be able to release RC3 this weekend. This will have
given us 2 weeks for reviewing RC2, and hopefully we can hold to the same
schedule for RC3. This would mean, if *all goes well*, we can release 2.7.1
on Saturday July 1.

In other words, Jython *2.7.1* on *2017-07-01*.

It's just like a long awaited summer movie :)

There was one additional bug report, http://bugs.jython.org/issue2598,
during the RC2 period. This issue is about using the ast module (or Java
equivalent) with ImportFrom AST nodes, specifically with relative imports,
since RC2 was released. However, this has been the case as the bug mentions
for 2.7.0 as well, so it is not a regression.

Although we should fix this bug, I do not believe this rises to a bug that
should block RC3 or the final release. Instead it can be deferred until
2.7.2, unless someone can produce an easy patch. But historically the
imp.java module is a bit of a challenge to work with, because there are so
many logic paths.

- Jim

On Wed, Jun 14, 2017 at 1:47 AM, <Tobias.Brieden@...> wrote:

> Thanks for the explanation!
>
>
>
> Tobias
>
>
>
> *Von:* jim.baker@... [mailto:jim.baker@...] *Im Auftrag
> von *Jim Baker
> *Gesendet:* Dienstag, 13. Juni 2017 21:00
> *An:* Brieden, Tobias
> *Cc:* Jython Developers
> *Betreff:* Re: [Jython-dev] Need for one more release candidate for
> Jython 2.7.1
>
>
>
> Tobias,
>
> I took a detailed look at http://bugs.jython.org/issue2513. Unfortunately
> there is no easy fix for this problem as stated, because org.python.jsr223.ScriptEngine,
> via org.python.util.PythonInterepreter, relies on
> org.python.core.PySystemState (= sys in Python), which effectively collects
> together global state for Python, either directly, such as sys.stdout, or
> indirectly, via sys.modules and any globals within those modules. The
> mechanism that ScriptEngine uses to put locals on a thread local will not
> work here, because this is maintained by a separate entity in Python, the
> frame object (= PyFrame in Jython); there is no such support for
> sys.stdout, etc, to be looked up from the thread.
>
> There is a possible solution, but it's not feasible at this point in the
> release cycle and needs to be deferred to later. Instead of always
> attempting to reuse PySystemState, Jython's JSR223 should instead support a
> model where new PySystemState objects can be attached to a ScriptEngine. I
> believe this is similar to what Nashorn supports with its
> --global-per-engine property (also configurable some other ways, see the
> notes). Regardless of exact similarity, this is how we would have to do it:
>
> ScriptEngine engine = factory.getScriptEngine(new String[] {
> "--global-per-engine" });
>
> (https://wiki.openjdk.java.net/display/Nashorn/Nashorn+jsr223+engine+notes
> )
>
> We should be able to implement this for 2.7.2; and also maybe we can speed
> up the cadence for 2.7.2. I don't see why that is not possible: a 6 month
> release cycle is still a very good idea, we just had too many problems we
> identified during 2.7.1 that kept pushing us back, plus changing time
> availability by contributors (certainly the case for me!).
>
> Lastly, for Jython 3, we may want to revisit some of our APIs like
> PySystemState so that they can be less global, lighter weight, and have
> better lifecycle management, while still maintaining their Python
> semantics. (So not easy!)
>
>
>
> - Jim
>
>
>
> On Tue, Jun 13, 2017 at 3:19 AM, <Tobias.Brieden@...> wrote:
>
> Is there any chance that a bug fix for issue 2513 [0] can still be
> included in Jython 2.7.1? This bug in Jython's JSR 223 implementation
> prevents parallel execution. Therefore, the execution of Jython scripts is
> in our application guarded by a global lock, which is a performance
> bottleneck. A fix would be a great improvement for us!
>
>
>
> Tobias
>
>
>
> [0] http://bugs.jython.org/issue2513
>
>
>
>
>
> *Von:* Jim Baker [mailto:jim.baker@...]
> *Gesendet:* Freitag, 9. Juni 2017 07:35
> *An:* Jython Developers; jython-users@...
> *Betreff:* [Jython-dev] Need for one more release candidate for Jython
> 2.7.1
>
>
>
> So it looks like we will need a RC3 for Jython 2.7.1, given the following
> two bugs:
>
>    - http://bugs.jython.org/issue2596 - Linebreaks in exceptions are
>    wrong - PENDING
>    - http://bugs.jython.org/issue2593 - file.write(obj) if obj is not a
>    str or buffer raises j.l.NullPointerException - OPEN
>
> #2596, now fixed in master, is just the sort of bug that may scramble
> existing user tests (although multi-line messages are relatively rare).
> #2593 has an easy path to raising a NullPointerException that can come up
> in common Python code. But it should be very straightforward to guard
> against, so we should have a fix for it momentarily I would assume.
>
>
>
> And that is it. There are exactly 301 other bugs that are open, as I write
> this email, so clearly we have plenty of work to consider in the future.
> But in my judgment, we are about there for a final release.
>
>
>
> But it's still not too late to submit a bug against RC2! Please test
> against the download links on Frank's blog post: http://fwierzbicki.
> blogspot.com/2017/06/jython-271-rc2-released.html
>
>
>
> - Jim
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>

Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1

[<Tobias.Brieden@dl...>]

Thanks for the explanation!

Tobias

Von: jim.baker@... [mailto:jim.baker@...] Im Auftrag von Jim Baker
Gesendet: Dienstag, 13. Juni 2017 21:00
An: Brieden, Tobias
Cc: Jython Developers
Betreff: Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1

Tobias,

I took a detailed look at http://bugs.jython.org/issue2513. Unfortunately there is no easy fix for this problem as stated, because org.python.jsr223.ScriptEngine, via org.python.util.PythonInterepreter, relies on org.python.core.PySystemState (= sys in Python), which effectively collects together global state for Python, either directly, such as sys.stdout, or indirectly, via sys.modules and any globals within those modules. The mechanism that ScriptEngine uses to put locals on a thread local will not work here, because this is maintained by a separate entity in Python, the frame object (= PyFrame in Jython); there is no such support for sys.stdout, etc, to be looked up from the thread.

There is a possible solution, but it's not feasible at this point in the release cycle and needs to be deferred to later. Instead of always attempting to reuse PySystemState, Jython's JSR223 should instead support a model where new PySystemState objects can be attached to a ScriptEngine. I believe this is similar to what Nashorn supports with its --global-per-engine property (also configurable some other ways, see the notes). Regardless of exact similarity, this is how we would have to do it:

ScriptEngine engine = factory.getScriptEngine(new String[] { "--global-per-engine" });

(https://wiki.openjdk.java.net/display/Nashorn/Nashorn+jsr223+engine+notes)

We should be able to implement this for 2.7.2; and also maybe we can speed up the cadence for 2.7.2. I don't see why that is not possible: a 6 month release cycle is still a very good idea, we just had too many problems we identified during 2.7.1 that kept pushing us back, plus changing time availability by contributors (certainly the case for me!).

Lastly, for Jython 3, we may want to revisit some of our APIs like PySystemState so that they can be less global, lighter weight, and have better lifecycle management, while still maintaining their Python semantics. (So not easy!)

- Jim

On Tue, Jun 13, 2017 at 3:19 AM, <Tobias.Brieden@...<mailto:Tobias.Brieden@...>> wrote:
Is there any chance that a bug fix for issue 2513 [0] can still be included in Jython 2.7.1? This bug in Jython's JSR 223 implementation prevents parallel execution. Therefore, the execution of Jython scripts is in our application guarded by a global lock, which is a performance bottleneck. A fix would be a great improvement for us!

Tobias

[0] http://bugs.jython.org/issue2513


Von: Jim Baker [mailto:jim.baker@...<mailto:jim.baker@...>]
Gesendet: Freitag, 9. Juni 2017 07:35
An: Jython Developers; jython-users@...<mailto:jython-users@...>
Betreff: [Jython-dev] Need for one more release candidate for Jython 2.7.1

So it looks like we will need a RC3 for Jython 2.7.1, given the following two bugs:

  *   http://bugs.jython.org/issue2596 - Linebreaks in exceptions are wrong - PENDING
  *   http://bugs.jython.org/issue2593 - file.write(obj) if obj is not a str or buffer raises j.l.NullPointerException - OPEN
#2596, now fixed in master, is just the sort of bug that may scramble existing user tests (although multi-line messages are relatively rare). #2593 has an easy path to raising a NullPointerException that can come up in common Python code. But it should be very straightforward to guard against, so we should have a fix for it momentarily I would assume.

And that is it. There are exactly 301 other bugs that are open, as I write this email, so clearly we have plenty of work to consider in the future. But in my judgment, we are about there for a final release.

But it's still not too late to submit a bug against RC2! Please test against the download links on Frank's blog post: http://fwierzbicki.blogspot.com/2017/06/jython-271-rc2-released.html

- Jim

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Jython-dev mailing list
Jython-dev@...<mailto:Jython-dev@...>
https://lists.sourceforge.net/lists/listinfo/jython-dev

Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1

[Jim Baker <jim.baker@py...>]

Tobias,

I took a detailed look at http://bugs.jython.org/issue2513. Unfortunately
there is no easy fix for this problem as stated, because
org.python.jsr223.ScriptEngine, via org.python.util.PythonInterepreter,
relies on org.python.core.PySystemState (= sys in Python), which
effectively collects together global state for Python, either directly,
such as sys.stdout, or indirectly, via sys.modules and any globals within
those modules. The mechanism that ScriptEngine uses to put locals on a
thread local will not work here, because this is maintained by a separate
entity in Python, the frame object (= PyFrame in Jython); there is no such
support for sys.stdout, etc, to be looked up from the thread.

There is a possible solution, but it's not feasible at this point in the
release cycle and needs to be deferred to later. Instead of always
attempting to reuse PySystemState, Jython's JSR223 should instead support a
model where new PySystemState objects can be attached to a ScriptEngine. I
believe this is similar to what Nashorn supports with its
--global-per-engine property (also configurable some other ways, see the
notes). Regardless of exact similarity, this is how we would have to do it:

ScriptEngine engine = factory.getScriptEngine(new String[] {
"--global-per-engine" });

(https://wiki.openjdk.java.net/display/Nashorn/Nashorn+jsr223+engine+notes)

We should be able to implement this for 2.7.2; and also maybe we can speed
up the cadence for 2.7.2. I don't see why that is not possible: a 6 month
release cycle is still a very good idea, we just had too many problems we
identified during 2.7.1 that kept pushing us back, plus changing time
availability by contributors (certainly the case for me!).

Lastly, for Jython 3, we may want to revisit some of our APIs like
PySystemState so that they can be less global, lighter weight, and have
better lifecycle management, while still maintaining their Python
semantics. (So not easy!)

- Jim

On Tue, Jun 13, 2017 at 3:19 AM, <Tobias.Brieden@...> wrote:

> Is there any chance that a bug fix for issue 2513 [0] can still be
> included in Jython 2.7.1? This bug in Jython's JSR 223 implementation
> prevents parallel execution. Therefore, the execution of Jython scripts is
> in our application guarded by a global lock, which is a performance
> bottleneck. A fix would be a great improvement for us!
>
>
>
> Tobias
>
>
>
> [0] http://bugs.jython.org/issue2513
>
>
>
>
>
> *Von:* Jim Baker [mailto:jim.baker@...]
> *Gesendet:* Freitag, 9. Juni 2017 07:35
> *An:* Jython Developers; jython-users@...
> *Betreff:* [Jython-dev] Need for one more release candidate for Jython
> 2.7.1
>
>
>
> So it looks like we will need a RC3 for Jython 2.7.1, given the following
> two bugs:
>
>    - http://bugs.jython.org/issue2596 - Linebreaks in exceptions are
>    wrong - PENDING
>    - http://bugs.jython.org/issue2593 - file.write(obj) if obj is not a
>    str or buffer raises j.l.NullPointerException - OPEN
>
> #2596, now fixed in master, is just the sort of bug that may scramble
> existing user tests (although multi-line messages are relatively rare).
> #2593 has an easy path to raising a NullPointerException that can come up
> in common Python code. But it should be very straightforward to guard
> against, so we should have a fix for it momentarily I would assume.
>
>
>
> And that is it. There are exactly 301 other bugs that are open, as I write
> this email, so clearly we have plenty of work to consider in the future.
> But in my judgment, we are about there for a final release.
>
>
>
> But it's still not too late to submit a bug against RC2! Please test
> against the download links on Frank's blog post: http://fwierzbicki.
> blogspot.com/2017/06/jython-271-rc2-released.html
>
>
>
> - Jim
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>

Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1

[Stefan Richthofer <Stefan.Richthofer@gm...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Tobias,</div>

<div>if you (or someone else) had a concrete fix for #2513 (or at least a precise idea how to fix it), ideally kind of a pull request, we can consider it.</div>

<div>Otherwise - given that nobody seems to be actively working on #2513 - and there is no totally obvious fix discribed in the threat, I&#39;m afraid chances would be quite minimal. At least AFAICT.</div>

<div>&nbsp;</div>

<div>- Stefan</div>

<div>&nbsp;
<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>&nbsp;Dienstag, 13. Juni 2017 um 11:19 Uhr<br/>
<b>Von:</b>&nbsp;Tobias.Brieden@...<br/>
<b>An:</b>&nbsp;jython-dev@...<br/>
<b>Betreff:</b>&nbsp;Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1</div>

<div name="quoted-content"><!--p.MsoNormal, li.MsoNormal, div.MsoNormal {
	margin: 0.0cm;
	font-size: 12.0pt;
	font-family: "Times New Roman" , serif;
}
a:link, span.MsoHyperlink {
	color: blue;
	text-decoration: underline;
}
a:visited, span.MsoHyperlinkFollowed {
	color: purple;
	text-decoration: underline;
}
span.gmail-il {
}
span.E-MailFormatvorlage18 {
	font-family: Calibri , sans-serif;
	color: rgb(31,73,125);
}
*.MsoChpDefault {
	font-family: Calibri , sans-serif;
}
div.WordSection1 {
	page: WordSection1;
}
ol {
	margin-bottom: 0.0cm;
}
ul {
	margin-bottom: 0.0cm;
}
-->
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">Is there any chance that a bug fix for issue 2513 [0] can still be included in Jython 2.7.1? This bug in Jython&#39;s JSR 223 implementation prevents parallel execution. Therefore, the execution of Jython scripts is in our application guarded by a global lock, which is a performance bottleneck. A fix would be a great improvement for us!</span></p>

<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">&nbsp;</span></p>

<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">Tobias</span></p>

<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">&nbsp;</span></p>

<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">[0] <a href="http://bugs.jython.org/issue2513"; target="_blank">http://bugs.jython.org/issue2513</a></span></p>;

<p class="MsoNormal"><span style="font-size: 11.0pt;font-family: Calibri , sans-serif;color: rgb(31,73,125);">&nbsp;</span></p>

<p class="MsoNormal"><span>&nbsp;</span></p>

<div style="border: none;border-left: solid blue 1.5pt;padding: 0.0cm 0.0cm 0.0cm 4.0pt;">
<div>
<div style="border: none;border-top: solid rgb(181,196,223) 1.0pt;padding: 3.0pt 0.0cm 0.0cm 0.0cm;">
<p class="MsoNormal"><b><span style="font-size: 10.0pt;font-family: Tahoma , sans-serif;">Von:</span></b><span style="font-size: 10.0pt;font-family: Tahoma , sans-serif;"> Jim Baker [mailto:jim.baker@...]<br/>
<b>Gesendet:</b> Freitag, 9. Juni 2017 07:35<br/>
<b>An:</b> Jython Developers; jython-users@...<br/>
<b>Betreff:</b> [Jython-dev] Need for one more release candidate for Jython 2.7.1</span></p>
</div>
</div>

<p class="MsoNormal">&nbsp;</p>

<div>
<p class="MsoNormal">So it looks like we will need a RC3 for Jython 2.7.1, given the following two bugs:</p>

<div>
<div>
<ul type="disc">
	<li class="MsoNormal"><a href="http://bugs.jython.org/issue2596"; target="_blank">http://bugs.jython.org/issue2596</a>; -&nbsp;Linebreaks in exceptions are wrong - PENDING</li>
	<li class="MsoNormal"><a href="http://bugs.jython.org/issue2593"; target="_blank">http://bugs.jython.org/issue2593</a>; -&nbsp;file.write(obj) if obj is not a str or buffer raises j.l.NullPointerException - OPEN</li>
</ul>
</div>
</div>

<div>
<p class="MsoNormal">#2596, now fixed in master, is just the sort of bug that may scramble existing user tests (although multi-line messages are relatively rare). #2593 has an easy path to raising a NullPointerException that can come up in common Python code. But it should be very straightforward to guard against, so we should have a fix for it momentarily I would assume.</p>
</div>

<div>
<p class="MsoNormal">&nbsp;</p>
</div>

<div>
<p class="MsoNormal">And that is it. There are exactly 301 other bugs that are open, as I write this email, so clearly we have plenty of work to consider in the future. But in my judgment, we are about there for a final release.</p>
</div>

<div>
<p class="MsoNormal">&nbsp;</p>
</div>

<div>
<p class="MsoNormal">But it&#39;s still not too late to submit a bug against RC2! Please test against the download links on Frank&#39;s blog post:&nbsp;<a href="http://fwierzbicki.blogspot.com/2017/06/jython-271-rc2-released.html"; target="_blank"><span style="font-size: 9.5pt;">http://fwierzbicki.blogspot.com/2017/06/<span class="gmail-il">jython</span>-271-<span class="gmail-il">rc2</span>-released.html</span></a></p>
</div>

<p class="MsoNormal">&nbsp;</p>

<div>
<p class="MsoNormal">- Jim</p>
</div>
</div>
</div>
</div>
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world&#39;s most engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot_______________________________________________"; target="_blank">http://sdm.link/slashdot_______________________________________________</a>; Jython-dev mailing list Jython-dev@... <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></body></html>

Re: [Jython-dev] Need for one more release candidate for Jython 2.7.1

[<Tobias.Brieden@dl...>]

Is there any chance that a bug fix for issue 2513 [0] can still be included in Jython 2.7.1? This bug in Jython's JSR 223 implementation prevents parallel execution. Therefore, the execution of Jython scripts is in our application guarded by a global lock, which is a performance bottleneck. A fix would be a great improvement for us!

Tobias

[0] http://bugs.jython.org/issue2513


Von: Jim Baker [mailto:jim.baker@...]
Gesendet: Freitag, 9. Juni 2017 07:35
An: Jython Developers; jython-users@...
Betreff: [Jython-dev] Need for one more release candidate for Jython 2.7.1

So it looks like we will need a RC3 for Jython 2.7.1, given the following two bugs:

  *   http://bugs.jython.org/issue2596 - Linebreaks in exceptions are wrong - PENDING
  *   http://bugs.jython.org/issue2593 - file.write(obj) if obj is not a str or buffer raises j.l.NullPointerException - OPEN
#2596, now fixed in master, is just the sort of bug that may scramble existing user tests (although multi-line messages are relatively rare). #2593 has an easy path to raising a NullPointerException that can come up in common Python code. But it should be very straightforward to guard against, so we should have a fix for it momentarily I would assume.

And that is it. There are exactly 301 other bugs that are open, as I write this email, so clearly we have plenty of work to consider in the future. But in my judgment, we are about there for a final release.

But it's still not too late to submit a bug against RC2! Please test against the download links on Frank's blog post: http://fwierzbicki.blogspot.com/2017/06/jython-271-rc2-released.html

- Jim

Re: [Jython-dev] Organisation of NEWS file

[<fwierzbicki@gm...>]

Big +1

On Sat, Jun 10, 2017 at 1:49 AM, Jeff Allen <ja.py@...> wrote:
> Routine business, but this keeps confusing me, and I feel I may sometimes
> have inserted things in the wrong place. However, this is helpful:
> https://docs.python.org/devguide/committing.html?highlight=news#what-s-new-and-news-entries
>
> From the perspective of the reader, I think he needs to read NEWS as saying
> "In release such-and-such, the bugs fixed are: <list of bugs>".
>
> It follows that we insert bugs fixed at the top, and definitely above the
> name of the last release actually made at the time the bug fix went in.
> Possibly we are inserting under the title of the next release in prospect.
> If we follow the branch-naming strategy here:
> https://docs.python.org/devguide/devcycle.html#branches , then we often know
> what that release is to be called. It would be acceptable (better?) not to
> have a title at all above the first bug-fixed entry, meaning that it exists
> in the development tip (of the branch where you found the NEWS file).
>
> Accordingly, I'm moving the rc1 heading down to where it seems to belong,
> judging from a quick look at the commit log, and inserting rc2 and rc3
> headings. Do  put me right (& fix) if you're sure this is incorrect.
>
> --
> Jeff Allen
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev

Re: [Jython-dev] Organisation of NEWS file

[Jim Baker <jim.baker@py...>]

Agreed with the approach of not putting a heading above dev tip. And NEWS
now looks good in terms of the specific cleanup you did. Thanks!

On Sat, Jun 10, 2017 at 2:49 AM, Jeff Allen <ja.py@...> wrote:

> Routine business, but this keeps confusing me, and I feel I may sometimes
> have inserted things in the wrong place. However, this is helpful:
> https://docs.python.org/devguide/committing.html?highlight=
> news#what-s-new-and-news-entries
>
> From the perspective of the reader, I think he needs to read NEWS as
> saying "In release such-and-such, the bugs fixed are: <list of bugs>".
>
> It follows that we insert bugs fixed at the top, and definitely above the
> name of the last release actually made at the time the bug fix went in.
> Possibly we are inserting under the title of the next release in prospect.
> If we follow the branch-naming strategy here:
> https://docs.python.org/devguide/devcycle.html#branches , then we often
> know what that release is to be called. It would be acceptable (better?)
> not to have a title at all above the first bug-fixed entry, meaning that it
> exists in the development tip (of the branch where you found the NEWS file).
>
> Accordingly, I'm moving the rc1 heading down to where it seems to belong,
> judging from a quick look at the commit log, and inserting rc2 and rc3
> headings. Do  put me right (& fix) if you're sure this is incorrect.
>
> --
> Jeff Allen
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jython-dev mailing list
> Jython-dev@...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

[Jython-dev] Organisation of NEWS file

[Jeff Allen <ja.py@fa...>]

Routine business, but this keeps confusing me, and I feel I may 
sometimes have inserted things in the wrong place. However, this is 
helpful: 
https://docs.python.org/devguide/committing.html?highlight=news#what-s-new-and-news-entries

 From the perspective of the reader, I think he needs to read NEWS as 
saying "In release such-and-such, the bugs fixed are: <list of bugs>".

It follows that we insert bugs fixed at the top, and definitely above 
the name of the last release actually made at the time the bug fix went 
in. Possibly we are inserting under the title of the next release in 
prospect. If we follow the branch-naming strategy here: 
https://docs.python.org/devguide/devcycle.html#branches , then we often 
know what that release is to be called. It would be acceptable (better?) 
not to have a title at all above the first bug-fixed entry, meaning that 
it exists in the development tip (of the branch where you found the NEWS 
file).

Accordingly, I'm moving the rc1 heading down to where it seems to 
belong, judging from a quick look at the commit log, and inserting rc2 
and rc3 headings. Do  put me right (& fix) if you're sure this is incorrect.

-- 
Jeff Allen

[Jython-dev] Summary of Jython tracker Issues

[Jython tracker <status@bu...>]

ACTIVITY SUMMARY (2017-06-02 - 2017-06-09)
Jython tracker at http://bugs.jython.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open     306 ( -6)
  closed  2310 ( +8)
  total   2616 ( +2)

Open issues with patches: 28   


Issues opened (2)
=================

#2596: Linebreaks in exceptions are wrong
http://bugs.jython.org/issue2596  opened by tkohn

#2597: Possible memory leak in Jython 2.7.1 RC2
http://bugs.jython.org/issue2597  opened by tobias



Most recent 15 issues with no replies (15)
==========================================

#2591: Unable to execute directory or zip file (test_cmd_line_script)
http://bugs.jython.org/issue2591

#2567: System state lost during JSR-223 initialisation
http://bugs.jython.org/issue2567

#2562: Windows: OSError: unlink(): an unknown error occurred
http://bugs.jython.org/issue2562

#2543: broken links for mailing list website
http://bugs.jython.org/issue2543

#2540: settrace doesn't notice "with" statements
http://bugs.jython.org/issue2540

#2531: Support SNI for SSL/TLS server sockets
http://bugs.jython.org/issue2531

#2525: Jython incorrectly buffers file pipe output with Subprocess(co
http://bugs.jython.org/issue2525

#2520: Jython does NOT support socket.listen(0) for accepting only on
http://bugs.jython.org/issue2520

#2512: Values in built-in modules's __dict__ are “<reflected field 
http://bugs.jython.org/issue2512

#2510: TypeError when monkey-patching time.time with an unbound funct
http://bugs.jython.org/issue2510

#2507: Run "invokeFunction" in a thread does not inherit the "ScriptC
http://bugs.jython.org/issue2507

#2494: Support for pydoc_data
http://bugs.jython.org/issue2494

#2484: Codec encodings can exhaust permgen
http://bugs.jython.org/issue2484

#2482: Publish U.S. ECCN for Jython
http://bugs.jython.org/issue2482

#2422: test_classpathimporter fauls on Linux
http://bugs.jython.org/issue2422



Most recent 15 issues waiting for review (15)
=============================================

#2566: inspect does not recognize code objects from bytecode files
http://bugs.jython.org/issue2566

#2545: help() does not work on Java-implemented modules
http://bugs.jython.org/issue2545

#2429: cStringIO does not work with mutable objects implementing the 
http://bugs.jython.org/issue2429

#2367: Jython ignores custom __eq__ when hashing dict subclasses
http://bugs.jython.org/issue2367

#2330: full-build fails to copy CPython License
http://bugs.jython.org/issue2330

#2230: Jython evaluation blocks under heavy load with high multi-core
http://bugs.jython.org/issue2230

#2143: site-packages support in standalone jar
http://bugs.jython.org/issue2143

#2142: Set Thread classloader when entering Jython context
http://bugs.jython.org/issue2142

#2121: Jython jar on Maven central embeds other third party libraries
http://bugs.jython.org/issue2121

#2077: marshal doesn't raise error when fed unmarshalable object
http://bugs.jython.org/issue2077

#1925: Support loading java.sql.Drivers that aren't on the boot class
http://bugs.jython.org/issue1925

#1917: No ctypes.c_char
http://bugs.jython.org/issue1917

#1866: Parser does not have mismatch token error messages caught by B
http://bugs.jython.org/issue1866

#1842: Add IBM i support to Jython
http://bugs.jython.org/issue1842

#1796: Jython doesn't support jar dir with colon's in it
http://bugs.jython.org/issue1796



Top 10 most discussed issues (1)
================================

#2596: Linebreaks in exceptions are wrong
http://bugs.jython.org/issue2596   3 msgs

[Jython-dev] Need for one more release candidate for Jython 2.7.1

[Jim Baker <jim.baker@py...>]

So it looks like we will need a RC3 for Jython 2.7.1, given the following
two bugs:

   - http://bugs.jython.org/issue2596 - Linebreaks in exceptions are wrong
   - PENDING
   - http://bugs.jython.org/issue2593 - file.write(obj) if obj is not a str
   or buffer raises j.l.NullPointerException - OPEN

#2596, now fixed in master, is just the sort of bug that may scramble
existing user tests (although multi-line messages are relatively rare).
#2593 has an easy path to raising a NullPointerException that can come up
in common Python code. But it should be very straightforward to guard
against, so we should have a fix for it momentarily I would assume.

And that is it. There are exactly 301 other bugs that are open, as I write
this email, so clearly we have plenty of work to consider in the future.
But in my judgment, we are about there for a final release.

But it's still not too late to submit a bug against RC2! Please test
against the download links on Frank's blog post:
http://fwierzbicki.blogspot.com/2017/06/jython-271-rc2-released.html

- Jim