jython-dev — Discussion of developing and enhancing Jython itself(!) (not how to use Jython)

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

[<fwi...@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

[<fwi...@gm...>]

On Sat, Jun 17, 2017 at 9:48 AM, fwi...@gm...
<fwi...@gm...> 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

[<fwi...@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 t. <st...@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'D. <ror...@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 B. <jim...@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, <Tob...@dl...> wrote:

> Thanks for the explanation!
>
>
>
> Tobias
>
>
>
> *Von:* jim...@zy... [mailto:jim...@zy...] *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, <Tob...@dl...> 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...@py...]
> *Gesendet:* Freitag, 9. Juni 2017 07:35
> *An:* Jython Developers; jyt...@li...
> *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
> 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
>
>

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

[<Tob...@dl...>]

Thanks for the explanation!

Tobias

Von: jim...@zy... [mailto:jim...@zy...] 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, <Tob...@dl...<mailto:Tob...@dl...>> 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...@py...<mailto:jim...@py...>]
Gesendet: Freitag, 9. Juni 2017 07:35
An: Jython Developers; jyt...@li...<mailto:jyt...@li...>
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
Jyt...@li...<mailto:Jyt...@li...>
https://lists.sourceforge.net/lists/listinfo/jython-dev

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

[Jim B. <jim...@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, <Tob...@dl...> 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...@py...]
> *Gesendet:* Freitag, 9. Juni 2017 07:35
> *An:* Jython Developers; jyt...@li...
> *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
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>

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

[Stefan R. <Ste...@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;Tob...@dl...<br/>
<b>An:</b>&nbsp;jyt...@li...<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...@py...]<br/>
<b>Gesendet:</b> Freitag, 9. Juni 2017 07:35<br/>
<b>An:</b> Jython Developers; jyt...@li...<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 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></div></body></html>

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

[<Tob...@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...@py...]
Gesendet: Freitag, 9. Juni 2017 07:35
An: Jython Developers; jyt...@li...
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

[<fwi...@gm...>]

Big +1

On Sat, Jun 10, 2017 at 1:49 AM, Jeff Allen <ja...@fa...> 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
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev

Re: [Jython-dev] Organisation of NEWS file

[Jim B. <jim...@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...@fa...> 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
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>

[Jython-dev] Organisation of NEWS file

[Jeff A. <ja...@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 t. <st...@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 B. <jim...@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

Re: [Jython-dev] Memory leak in Jython 2.7.1 RC2?

[Stefan R. <Ste...@gm...>]

Tobias,
 
in http://bugs.jython.org/issue2597 I suggest a simple solution for this bug. If that turns out to be sufficient, a fix is straight forward. I suppose 2.7.1 RC2 cannot turn into final already because of http://bugs.jython.org/issue2596.
If nobody objects that we will need an RC3 phase, #2597 will be fixed then for 2.7.1.
However, we should wait a while to see if more stuff for RC3 pops up.

-Stefan
 

Gesendet: Mittwoch, 07. Juni 2017 um 09:16 Uhr
Von: Tob...@dl...
An: jyt...@li...
Betreff: Re: [Jython-dev] Memory leak in Jython 2.7.1 RC2?

I created a bug report: http://bugs.jython.org/issue2597[http://bugs.jython.org/issue2597]
 
By the way, is there any chance that the bug mentioned the following bug report is tackled in 2.7.1?:  http://bugs.jython.org/issue2513[http://bugs.jython.org/issue2513]
 

 
Tobias
 

Von: Stefan Richthofer [mailto:Ste...@gm...]
Gesendet: Freitag, 2. Juni 2017 14:17
An: Brieden, Tobias
Cc: Jython Developers
Betreff: Re: [Jython-dev] Memory leak in Jython 2.7.1 RC2?
 

Tobias,

thanks for testing 2.7.1 RC2!

I'd recommend to file this as a new issue on bugs.jython.org.

It is better tracked there and not so likely to get lost. We can have additional discussion there.

 

Best

 

-Stefan

 

Gesendet: Donnerstag, 01. Juni 2017 um 13:00 Uhr
Von: Tob...@dl...[mailto:Tob...@dl...]
An: jyt...@li...[mailto:jyt...@li...]
Betreff: [Jython-dev] Memory leak in Jython 2.7.1 RC2?

Hi,
 
we are using Jython embedded in an Open Source Java application to allow our users to script certain behavior. We are really looking forward to the release of Jython 2.7.1, since we are currently using Jython 2.5.1 and weren't able to upgrade in the meantime due to various Jython bugs. Therefore, I am lurking on the developer mailing list to be up to date with the current development and I wanted to give you some early feedback to the RC2 of 2.7.1.
 
One problem we encountered in an earlier Jython version (2.5.2) was the memory leak described in this bug report: http://bugs.jython.org/issue2026[http://bugs.jython.org/issue2026] . The bug is marked as fixed and I wanted to double check this. Therefore, I used the code snipped contained in the bug report to reconstruct the issue. The original issue seems to be resolved, but I encountered another problem. If I run the aforementioned code for a short period of time, the consumed heap increases quite fast: ~120MB after ~60 seconds. I inspected the heap dump and most the memory is consumed by a ConcurrentHashMap in PySystemState. I took a quick peek at the source and found this:
 
PySystemState has a static final ConcurrentHashMap named sysClosers [0]. If a new PySystemStateCloser is created, a Key-Value-Pair of a WeakReference to a PySystemState and a reference to the PySystemStateCloser is added to the map [1], but never removed. Even if the WeakReference is finalized, if looks like the value will still remain in the map, since there is no removal code for broken references.
 
 
I haven't created a bug report for this issue, since the RC is not officially announced, but I can do this if requested.
 
 
Thanks for your efforts!
 
Tobias
 
 
[0] https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l199[https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l199]
[1] https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l1575[https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l1575]
 
 
------------------------------------------------------------------------------ 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
------------------------------------------------------------------------------ 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... https://lists.sourceforge.net/lists/listinfo/jython-dev[https://lists.sourceforge.net/lists/listinfo/jython-dev]

Re: [Jython-dev] Memory leak in Jython 2.7.1 RC2?

[<Tob...@dl...>]

I created a bug report: http://bugs.jython.org/issue2597

By the way, is there any chance that the bug mentioned the following bug report is tackled in 2.7.1?:  http://bugs.jython.org/issue2513


Tobias

Von: Stefan Richthofer [mailto:Ste...@gm...]
Gesendet: Freitag, 2. Juni 2017 14:17
An: Brieden, Tobias
Cc: Jython Developers
Betreff: Re: [Jython-dev] Memory leak in Jython 2.7.1 RC2?

Tobias,
thanks for testing 2.7.1 RC2!
I'd recommend to file this as a new issue on bugs.jython.org.
It is better tracked there and not so likely to get lost. We can have additional discussion there.

Best

-Stefan

Gesendet: Donnerstag, 01. Juni 2017 um 13:00 Uhr
Von: Tob...@dl...<mailto:Tob...@dl...>
An: jyt...@li...<mailto:jyt...@li...>
Betreff: [Jython-dev] Memory leak in Jython 2.7.1 RC2?
Hi,

we are using Jython embedded in an Open Source Java application to allow our users to script certain behavior. We are really looking forward to the release of Jython 2.7.1, since we are currently using Jython 2.5.1 and weren't able to upgrade in the meantime due to various Jython bugs. Therefore, I am lurking on the developer mailing list to be up to date with the current development and I wanted to give you some early feedback to the RC2 of 2.7.1.

One problem we encountered in an earlier Jython version (2.5.2) was the memory leak described in this bug report: http://bugs.jython.org/issue2026 . The bug is marked as fixed and I wanted to double check this. Therefore, I used the code snipped contained in the bug report to reconstruct the issue. The original issue seems to be resolved, but I encountered another problem. If I run the aforementioned code for a short period of time, the consumed heap increases quite fast: ~120MB after ~60 seconds. I inspected the heap dump and most the memory is consumed by a ConcurrentHashMap in PySystemState. I took a quick peek at the source and found this:

PySystemState has a static final ConcurrentHashMap named sysClosers [0]. If a new PySystemStateCloser is created, a Key-Value-Pair of a WeakReference to a PySystemState and a reference to the PySystemStateCloser is added to the map [1], but never removed. Even if the WeakReference is finalized, if looks like the value will still remain in the map, since there is no removal code for broken references.


I haven't created a bug report for this issue, since the RC is not officially announced, but I can do this if requested.


Thanks for your efforts!

Tobias


[0] https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l199
[1] https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l1575


------------------------------------------------------------------------------ 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

[Jython-dev] Coding standards

[Jeff A. <ja...@fa...>]

Possibly a yawn-worthy topic for some, or a rich source of flame-wars. 
There is a practical issue: when we're creating change-sets, and reading 
them, there will be a lot more change to read if each of our IDEs is 
normalising to a different set of conventions. [1]

We have this page: https://wiki.python.org/jython/CodingStandards on the 
not-much-loved Wiki. Apart from some project-specific preferences, the 
main thing it says is "follow the Sun Java Coding Conventions". The link 
is broken (again) but I found them here: 
http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html

They still look good to me, but are not maintained (why not?).

The other thing we've done is to provide an Eclipse formatting profile 
(thanks to Charlie Groves in 2008). I use Eclipse and I found this 
mostly satisfactory except when it comes to line-wrapping. For method 
calls and declarations, it likes each argument on a new line, in which 
it contradicts the Sun conventions we just recommended. This is also not 
what we find in most of the code base either, so my variant wraps like 
Sun's "indent at 8 spaces". 
(http://www.oracle.com/technetwork/java/javase/documentation/codeconventions-136091.html#248). 
It's mostly line-wrapping issues that have me tweaking the formatter. 
Also, I made choices about features new since 2008 (lambda, 
try-with-resources) where the default seemed inconsistent with other 
formatting.

I have some save actions set in Eclipse, like adding {} to if clauses, 
@Override where recommended, and stripping trailing space (which I find 
it puts in easily), but they don't get saved as part of the formatter.

If no-one objects, I'll post this slightly tweaked formatter. It's not 
much different, honest. I did this once before, but I think we lost it 
in the great defacement.

We should recommend this page to contributors who seem not to be aware 
of it. Can we help them with formatters from other IDEs that enforce 
more-or-less the same standard?

Jeff


[1] For this reason, if I spot that there will be a lot of reformatting 
of some files, I make that reformatting first in a change set of its 
own, so it can be ignored.

-- 
Jeff Allen

Re: [Jython-dev] Building Jython3

[Jim B. <jim...@py...>]

+1 to logical commits

I'm looking forward to using branches, vs having to carefully prep diffs.
BitBucket PRs in particular didn't work well with hg.python.org's gate.
Very tedious and time consuming, which unfortunately meant reviews took
forever.

On Jun 3, 2017 9:44 AM, "Douglas Clayton" <dcl...@cy...>
wrote:

>
> On Sat, Jun 3, 2017 at 5:15 AM Jeff Allen <ja...@fa...> wrote:
>
>> Git gives us a lot of possibilities for squeezing out, at the PR stage or
>> before, the noise-commits caused by merges and development choices later
>> reverted. But let's only squash things together that belong together, and
>> not be afraid to show key points on the journey to a feature if it aids
>> others. This would all make reviewing a change easier.
>>
>
> I have only contributed a few patches to Jython, but I have used git
> extensively for many years. I think Jeff's summary here is exactly the
> right approach: expect developers to clean up the noise and the false
> starts, but keep the "key points" that make the change intelligible to
> others. Github's squash merges flatten everything down, regardless of
> whether that clarifies or confuses the nature of the change. Learning how
> to do the "interactive rebase" for this definitely has a learning curve,
> but it pays off pretty quickly in keeping the history understandable.
>
>
> Doug
>
>
>

Re: [Jython-dev] Building Jython3

[Jim B. <jim...@py...>]

Good tip. This works for me on OSX:

$ PYTHONIOENCODING=ascii dist/bin/jython -S
Jython 3.5.1a1+ (, Jun 3 2017, 21:59:14)
[Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation)] on java1.8.0_112
>>> print(42)
42
>>>

We have some work in front of us to really get past this point.

On Sun, Jun 4, 2017 at 5:54 AM, Jeff Allen <ja...@fa...> wrote:

> I find I can get as far as a REPL prompt with -S if I force the console
> encoding to ascii, and this will let me investigate the problems with
> import -- if that's not duplicating anyone else.
> Jeff
>
> Jeff Allen
>
> On 31/05/2017 22:09, Jeff Allen wrote:
>
> It fails either way for me (-S or not), and with the same error Isaiah
> reports. However, I'm just impressed it compiles the 3.5 std lib.
>
> When I say "the same error", I can tell that from debug, but in fact it
> dies trying to print the error because it can't find the right codec
> (cp850). I'm not phased though, as I've solved that before. (
> https://hg.python.org/jython/file/tip/src/org/python/core/Py.java#l1345)
> Lot's to chew on here.
>
> Jeff
>
> Jeff Allen
>
> On 31/05/2017 21:29, Isaiah Peng wrote:
>
> Hi Frank,
>
> Looks like the master branch is force pushed, if I run `dist/bin/jython
> -S` it shows a stacktrace:
>
> TypeError: org.python.modules.zipimport.PyZipImporter(): 1st arg can't be
> coerced to org.python.core.PyType
> Exception in thread "main" java.util.NoSuchElementException
>
> at java.util.LinkedList.removeFirst(LinkedList.java:
> 270)
>                                    at java.util.LinkedList.pop(
> LinkedList.java:801)
>         at org.python.core.Py.printException(Py.java:1420)
>
>         at org.python.core.Py.printException(Py.java:1362)
>
>         at org.python.util.jython.run(jython.java:419)
>
>
>         at org.python.util.jython.main(jython.java:141)
>
>
> However, when I try the old HEAD `9fae4ae17d27b540b6c22707317fd3c8d83d8cfe`,
> it can actually run without `-S`, but since I only have a linux machine,
> cannot grantee that you'll get the same result on other OS.
>
> (git)-[9fae4ae...] % dist/bin/jython
>
> Listening for transport dt_socket at address:
> 5005
>
> Jython 3.5.1a1+ (, Mai 31 2017, 22:20:58)
>
>
> [Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation)] on java1.8.0_131
> Type "help", "copyright", "credits" or "license" for more
> information.
>
> >>>
>
> A side note, don't use java9, the bootstrap process needs some change to
> be able to load java packages from java modules, as there is no more rt.jar
> exists.
>
> Hope that helps.
> Isaiah
>
> On Wed, 31 May 2017 at 09:57 Isaiah Peng <is...@gm...> wrote:
>
>> Hi,
>>
>> Congratulation on the new release of Jython 2.7.
>>
>> For the build issue on windows, it should be some jnr-posix call in
>> PosixModule not masked for windows platform.
>>
>> Regarding gradle integration if we simply wants to fix the dependency
>> management, we could improve the ivy task that's already included in the
>> project.
>>
>> > UncaughtExceptionHandler in thread "main"
>> I'll try to figure out today
>>
>> Best,
>> Isaiah
>>
>> On Wed, 31 May 2017 at 02:51 fwi...@gm... <fwi...@gm...>
>> wrote:
>>
>>> Starting a new thread, and including Isaiah Peng in case he has some
>>> insights. Hi Isaiah! We are starting to discuss how to make the
>>> Jython3 sandbox the main line for development after the Jython 2.7.1
>>> release.
>>>
>>> On Tue, May 30, 2017 at 6:39 AM, Jeff Allen <ja...@fa...> wrote:
>>> > Part of me wants to pursue it, but not as much as making Jython 3
>>> build.
>>>
>>> I took a look, and made a couple of changes that get Jython3 building
>>> for me, so the tip of https://github.com/jython/jython3 should now
>>> build (I hope).
>>>
>>> For me though, it does not run. I always get:
>>>
>>> $ ./dist/bin/jython
>>> Exception in thread "main"
>>> Exception: java.lang.NullPointerException thrown from the
>>> UncaughtExceptionHandler in thread "main"
>>>
>>> Investigating further, the issue seems to have been introduced on Sept
>>> 19 in this commit, which unfortunately, is a biggish one:
>>>
>>> """
>>> commit 308a17a4e9972aa3814a358917ffbd25fd976864
>>> Author: Isaiah Peng <is...@gm...>
>>> Date:   Mon Sep 19 18:13:57 2016 +0200
>>>
>>>     rewrite zipimporter, detach from the shared importer abstract
>>> class, since classpathpyimporter is currently not functional
>>> """
>>>
>>> The last commit that works on my machine is the one just before:
>>>
>>> """
>>> commit cfed7ce10083ca69f2cec19b9a73d78b60e13967
>>> Author: Isaiah Peng <is...@gm...>
>>> Date:   Mon Sep 19 15:24:04 2016 +0200
>>>
>>>     throw OSError for negative seek position
>>> """
>>>
>>> Hope this helps!
>>>
>>> -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 lis...@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
>
>

Re: [Jython-dev] Building Jython3

[Jeff A. <ja...@fa...>]

I find I can get as far as a REPL prompt with -S if I force the console 
encoding to ascii, and this will let me investigate the problems with 
import -- if that's not duplicating anyone else.

Jeff

Jeff Allen

On 31/05/2017 22:09, Jeff Allen wrote:
>
> It fails either way for me (-S or not), and with the same error Isaiah 
> reports. However, I'm just impressed it compiles the 3.5 std lib.
>
> When I say "the same error", I can tell that from debug, but in fact 
> it dies trying to print the error because it can't find the right 
> codec (cp850). I'm not phased though, as I've solved that before. 
> (https://hg.python.org/jython/file/tip/src/org/python/core/Py.java#l1345) 
> Lot's to chew on here.
>
> Jeff
>
> Jeff Allen
> On 31/05/2017 21:29, Isaiah Peng wrote:
>> Hi Frank,
>>
>> Looks like the master branch is force pushed, if I run 
>> `dist/bin/jython -S` it shows a stacktrace:
>>
>> TypeError: org.python.modules.zipimport.PyZipImporter(): 1st arg 
>> can't be coerced to org.python.core.PyType
>> Exception in thread "main" java.util.NoSuchElementException at 
>> java.util.LinkedList.removeFirst(LinkedList.java:270) at 
>> java.util.LinkedList.pop(LinkedList.java:801)
>>         at org.python.core.Py.printException(Py.java:1420)
>>         at org.python.core.Py.printException(Py.java:1362)
>>         at org.python.util.jython.run(jython.java:419)
>>         at org.python.util.jython.main(jython.java:141)
>>
>> However, when I try the old HEAD 
>> `9fae4ae17d27b540b6c22707317fd3c8d83d8cfe`, it can actually run 
>> without `-S`, but since I only have a linux machine, cannot grantee 
>> that you'll get the same result on other OS.
>>
>> (git)-[9fae4ae...] % dist/bin/jython
>> Listening for transport dt_socket at address: 5005
>> Jython 3.5.1a1+ (, Mai 31 2017, 22:20:58)
>> [Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation)] on java1.8.0_131
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>>
>>
>> A side note, don't use java9, the bootstrap process needs some change 
>> to be able to load java packages from java modules, as there is no 
>> more rt.jar exists.
>>
>> Hope that helps.
>> Isaiah
>>
>> On Wed, 31 May 2017 at 09:57 Isaiah Peng <is...@gm... 
>> <mailto:is...@gm...>> wrote:
>>
>>     Hi,
>>
>>     Congratulation on the new release of Jython 2.7.
>>
>>     For the build issue on windows, it should be some jnr-posix call
>>     in PosixModule not masked for windows platform.
>>
>>     Regarding gradle integration if we simply wants to fix the
>>     dependency management, we could improve the ivy task that's
>>     already included in the project.
>>
>>     > UncaughtExceptionHandler in thread "main"
>>     I'll try to figure out today
>>
>>     Best,
>>     Isaiah
>>
>>     On Wed, 31 May 2017 at 02:51 fwi...@gm...
>>     <mailto:fwi...@gm...> <fwi...@gm...
>>     <mailto:fwi...@gm...>> wrote:
>>
>>         Starting a new thread, and including Isaiah Peng in case he
>>         has some
>>         insights. Hi Isaiah! We are starting to discuss how to make the
>>         Jython3 sandbox the main line for development after the
>>         Jython 2.7.1
>>         release.
>>
>>         On Tue, May 30, 2017 at 6:39 AM, Jeff Allen
>>         <ja...@fa... <mailto:ja...@fa...>> wrote:
>>         > Part of me wants to pursue it, but not as much as making
>>         Jython 3 build.
>>
>>         I took a look, and made a couple of changes that get Jython3
>>         building
>>         for me, so the tip of https://github.com/jython/jython3
>>         should now
>>         build (I hope).
>>
>>         For me though, it does not run. I always get:
>>
>>         $ ./dist/bin/jython
>>         Exception in thread "main"
>>         Exception: java.lang.NullPointerException thrown from the
>>         UncaughtExceptionHandler in thread "main"
>>
>>         Investigating further, the issue seems to have been
>>         introduced on Sept
>>         19 in this commit, which unfortunately, is a biggish one:
>>
>>         """
>>         commit 308a17a4e9972aa3814a358917ffbd25fd976864
>>         Author: Isaiah Peng <is...@gm...
>>         <mailto:is...@gm...>>
>>         Date:   Mon Sep 19 18:13:57 2016 +0200
>>
>>             rewrite zipimporter, detach from the shared importer abstract
>>         class, since classpathpyimporter is currently not functional
>>         """
>>
>>         The last commit that works on my machine is the one just before:
>>
>>         """
>>         commit cfed7ce10083ca69f2cec19b9a73d78b60e13967
>>         Author: Isaiah Peng <is...@gm...
>>         <mailto:is...@gm...>>
>>         Date:   Mon Sep 19 15:24:04 2016 +0200
>>
>>             throw OSError for negative seek position
>>         """
>>
>>         Hope this helps!
>>
>>         -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
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev

Re: [Jython-dev] Building Jython3

[Douglas C. <dcl...@cy...>]

On Sat, Jun 3, 2017 at 5:15 AM Jeff Allen <ja...@fa...> wrote:

> Git gives us a lot of possibilities for squeezing out, at the PR stage or
> before, the noise-commits caused by merges and development choices later
> reverted. But let's only squash things together that belong together, and
> not be afraid to show key points on the journey to a feature if it aids
> others. This would all make reviewing a change easier.
>

I have only contributed a few patches to Jython, but I have used git
extensively for many years. I think Jeff's summary here is exactly the
right approach: expect developers to clean up the noise and the false
starts, but keep the "key points" that make the change intelligible to
others. Github's squash merges flatten everything down, regardless of
whether that clarifies or confuses the nature of the change. Learning how
to do the "interactive rebase" for this definitely has a learning curve,
but it pays off pretty quickly in keeping the history understandable.


Doug

Re: [Jython-dev] Building Jython3

[Jeff A. <ja...@fa...>]

On 31/05/2017 04:35, Jim Baker wrote:
> Thanks for kicking this specific discussion off. Some points:
>
> 1. We can switch to github now if we focus on Jython 3. I would 
> suggest using squash merges 
> (https://github.com/blog/2141-squash-your-commits 
> <https://github.com/blog/2141-squash-your-commits>). Then over time we 
> can adopt CPython core workflow.
I think this is good advice when we adopt the the git philosophy of 
topic-branching frequently committing. (We should.) With Mercurial, 
branching was discouraged (prohibited in the push, I think). Git gives 
us a lot of possibilities for squeezing out, at the PR stage or before, 
the noise-commits caused by merges and development choices later 
reverted. But let's only squash things together that belong together, 
and not be afraid to show key points on the journey to a feature if it 
aids others. This would all make reviewing a change easier.

I will continue using the CPython workflow (on the Jython 3 sandpit) 
experimentally. The missing part is the tools CPython created: labels, 
bots, and the linkage to the bug tracker.

> 2. We should bring in the Gradle build process that Darjus is working 
> on, and get that into Jython 3 as soon as possible.
I'd be happy to adopt that when it's ready, but would like to get on 
with code.

> 3. Once we finish pushing the 2.7 changes into Jython 3, hopefully 
> automated as Stefan suggests, we should backport going forward into 
> 2.7 (some changes will have to be made against 2.7 of course). Having 
> everything in https://github.com/jython/jython, with a branch for 2.7, 
> should simplify; and follows the CPython model. This means Jython 3 
> will take advantage of the planned history rewriting.
Good reminder. Playing back to be sure I've understood ... At present 
Jython 3 lives separately from the official Jython repository. The 
desirable state is as Jim says to replicate the CPython pattern 
(https://docs.python.org/devguide/devcycle.html#branches) on the 
official Jython repo (https://github.com/jython/jython), where if I've 
understood correctly, Jython 2.7 (current master) becomes a 2.7 branch, 
and we bring in the present state of https://github.com/jython/jython3 
as the new master. This would give us CI tests on Jython 3 that we 
presently lack.

I sense we might like to squash some of that into fewer "feature" 
commits, but _not_ down to one massive one. This sounds like hard 
labour, maybe too hard.

Not sure I understand the scope of "the intended history re-writing".

  Jeff

>
> On Tue, May 30, 2017 at 6:50 PM, fwi...@gm... 
> <mailto:fwi...@gm...> <fwi...@gm... 
> <mailto:fwi...@gm...>> wrote:
>
>     Starting a new thread, and including Isaiah Peng in case he has some
>     insights. Hi Isaiah! We are starting to discuss how to make the
>     Jython3 sandbox the main line for development after the Jython 2.7.1
>     release.
>
>     On Tue, May 30, 2017 at 6:39 AM, Jeff Allen <ja...@fa...
>     <mailto:ja...@fa...>> wrote:
>     > Part of me wants to pursue it, but not as much as making Jython
>     3 build.
>
>     I took a look, and made a couple of changes that get Jython3 building
>     for me, so the tip of https://github.com/jython/jython3
>     <https://github.com/jython/jython3> should now
>     build (I hope).
>
>     For me though, it does not run. I always get:
>
>     $ ./dist/bin/jython
>     Exception in thread "main"
>     Exception: java.lang.NullPointerException thrown from the
>     UncaughtExceptionHandler in thread "main"
>
>     Investigating further, the issue seems to have been introduced on Sept
>     19 in this commit, which unfortunately, is a biggish one:
>
>     """
>     commit 308a17a4e9972aa3814a358917ffbd25fd976864
>     Author: Isaiah Peng <is...@gm... <mailto:is...@gm...>>
>     Date:   Mon Sep 19 18:13:57 2016 +0200
>
>         rewrite zipimporter, detach from the shared importer abstract
>     class, since classpathpyimporter is currently not functional
>     """
>
>     The last commit that works on my machine is the one just before:
>
>     """
>     commit cfed7ce10083ca69f2cec19b9a73d78b60e13967
>     Author: Isaiah Peng <is...@gm... <mailto:is...@gm...>>
>     Date:   Mon Sep 19 15:24:04 2016 +0200
>
>         throw OSError for negative seek position
>     """
>
>     Hope this helps!
>
>     -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
>     Jyt...@li...
>     <mailto:Jyt...@li...>
>     https://lists.sourceforge.net/lists/listinfo/jython-dev
>     <https://lists.sourceforge.net/lists/listinfo/jython-dev>
>
>

Re: [Jython-dev] Building Jython3

[Jeff A. <ja...@fa...>]

I'm not sure I understand the relevance of "force pushed" as an 
explanation. However, it now builds for me in a version fetched from 
https://github.com/jython/jython3. I managed this change by following 
the CPython dev guide. (See https://github.com/jython/jython3/pull/29, 
and the thread I started about that process.) It was a bit long-winded, 
but the first time is not representative.

I'll turn to making sure I can get a meaningful stack trace out on 
Windows first, as the issue here is encoding -- familiar territory now 
-- and it is a prerequisite for other progress.

Jeff

Jeff Allen

On 31/05/2017 22:09, Jeff Allen wrote:
>
> It fails either way for me (-S or not), and with the same error Isaiah 
> reports. However, I'm just impressed it compiles the 3.5 std lib.
>
> When I say "the same error", I can tell that from debug, but in fact 
> it dies trying to print the error because it can't find the right 
> codec (cp850). I'm not phased though, as I've solved that before. 
> (https://hg.python.org/jython/file/tip/src/org/python/core/Py.java#l1345) 
> Lot's to chew on here.
>
> Jeff
>
> Jeff Allen
> On 31/05/2017 21:29, Isaiah Peng wrote:
>> Hi Frank,
>>
>> Looks like the master branch is force pushed, if I run 
>> `dist/bin/jython -S` it shows a stacktrace:
>>
>> TypeError: org.python.modules.zipimport.PyZipImporter(): 1st arg 
>> can't be coerced to org.python.core.PyType
>> Exception in thread "main" java.util.NoSuchElementException at 
>> java.util.LinkedList.removeFirst(LinkedList.java:270) at 
>> java.util.LinkedList.pop(LinkedList.java:801)
>>         at org.python.core.Py.printException(Py.java:1420)
>>         at org.python.core.Py.printException(Py.java:1362)
>>         at org.python.util.jython.run(jython.java:419)
>>         at org.python.util.jython.main(jython.java:141)
>>
>> However, when I try the old HEAD 
>> `9fae4ae17d27b540b6c22707317fd3c8d83d8cfe`, it can actually run 
>> without `-S`, but since I only have a linux machine, cannot grantee 
>> that you'll get the same result on other OS.
>>
>> (git)-[9fae4ae...] % dist/bin/jython
>> Listening for transport dt_socket at address: 5005
>> Jython 3.5.1a1+ (, Mai 31 2017, 22:20:58)
>> [Java HotSpot(TM) 64-Bit Server VM (Oracle Corporation)] on java1.8.0_131
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>>
>>
>> A side note, don't use java9, the bootstrap process needs some change 
>> to be able to load java packages from java modules, as there is no 
>> more rt.jar exists.
>>
>> Hope that helps.
>> Isaiah
>>
>> On Wed, 31 May 2017 at 09:57 Isaiah Peng <is...@gm... 
>> <mailto:is...@gm...>> wrote:
>>
>>     Hi,
>>
>>     Congratulation on the new release of Jython 2.7.
>>
>>     For the build issue on windows, it should be some jnr-posix call
>>     in PosixModule not masked for windows platform.
>>
>>     Regarding gradle integration if we simply wants to fix the
>>     dependency management, we could improve the ivy task that's
>>     already included in the project.
>>
>>     > UncaughtExceptionHandler in thread "main"
>>     I'll try to figure out today
>>
>>     Best,
>>     Isaiah
>>
>>     On Wed, 31 May 2017 at 02:51 fwi...@gm...
>>     <mailto:fwi...@gm...> <fwi...@gm...
>>     <mailto:fwi...@gm...>> wrote:
>>
>>         Starting a new thread, and including Isaiah Peng in case he
>>         has some
>>         insights. Hi Isaiah! We are starting to discuss how to make the
>>         Jython3 sandbox the main line for development after the
>>         Jython 2.7.1
>>         release.
>>
>>         On Tue, May 30, 2017 at 6:39 AM, Jeff Allen
>>         <ja...@fa... <mailto:ja...@fa...>> wrote:
>>         > Part of me wants to pursue it, but not as much as making
>>         Jython 3 build.
>>
>>         I took a look, and made a couple of changes that get Jython3
>>         building
>>         for me, so the tip of https://github.com/jython/jython3
>>         should now
>>         build (I hope).
>>
>>         For me though, it does not run. I always get:
>>
>>         $ ./dist/bin/jython
>>         Exception in thread "main"
>>         Exception: java.lang.NullPointerException thrown from the
>>         UncaughtExceptionHandler in thread "main"
>>
>>         Investigating further, the issue seems to have been
>>         introduced on Sept
>>         19 in this commit, which unfortunately, is a biggish one:
>>
>>         """
>>         commit 308a17a4e9972aa3814a358917ffbd25fd976864
>>         Author: Isaiah Peng <is...@gm...
>>         <mailto:is...@gm...>>
>>         Date:   Mon Sep 19 18:13:57 2016 +0200
>>
>>             rewrite zipimporter, detach from the shared importer abstract
>>         class, since classpathpyimporter is currently not functional
>>         """
>>
>>         The last commit that works on my machine is the one just before:
>>
>>         """
>>         commit cfed7ce10083ca69f2cec19b9a73d78b60e13967
>>         Author: Isaiah Peng <is...@gm...
>>         <mailto:is...@gm...>>
>>         Date:   Mon Sep 19 15:24:04 2016 +0200
>>
>>             throw OSError for negative seek position
>>         """
>>
>>         Hope this helps!
>>
>>         -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
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev

Re: [Jython-dev] Jython 2.7.1 rc2 released!

[<fwi...@gm...>]

On behalf of the Jython development team, I'm pleased to announce that
Jython 2.7.1 rc2 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-rc2-released.html

-Frank