Menu
▾
▴
jython-dev — Discussion of developing and enhancing Jython itself(!) (not how to use Jython)
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(38) |
Nov
(98) |
Dec
(58) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(114) |
Feb
(123) |
Mar
(96) |
Apr
(66) |
May
(84) |
Jun
(72) |
Jul
(128) |
Aug
(126) |
Sep
(82) |
Oct
(80) |
Nov
(148) |
Dec
(55) |
| 2002 |
Jan
(137) |
Feb
(85) |
Mar
(118) |
Apr
(67) |
May
(71) |
Jun
(28) |
Jul
(69) |
Aug
(48) |
Sep
(83) |
Oct
(79) |
Nov
(54) |
Dec
(32) |
| 2003 |
Jan
(44) |
Feb
(47) |
Mar
(59) |
Apr
(57) |
May
(43) |
Jun
(45) |
Jul
(44) |
Aug
(39) |
Sep
(27) |
Oct
(62) |
Nov
(17) |
Dec
(23) |
| 2004 |
Jan
(41) |
Feb
(51) |
Mar
(38) |
Apr
(30) |
May
(25) |
Jun
(12) |
Jul
(11) |
Aug
(27) |
Sep
(16) |
Oct
(56) |
Nov
(23) |
Dec
(29) |
| 2005 |
Jan
(75) |
Feb
(82) |
Mar
(50) |
Apr
(77) |
May
(19) |
Jun
(104) |
Jul
(47) |
Aug
(42) |
Sep
(28) |
Oct
(143) |
Nov
(62) |
Dec
(13) |
| 2006 |
Jan
(20) |
Feb
(10) |
Mar
(59) |
Apr
(45) |
May
(25) |
Jun
(129) |
Jul
(162) |
Aug
(91) |
Sep
(15) |
Oct
(39) |
Nov
(186) |
Dec
(191) |
| 2007 |
Jan
(134) |
Feb
(140) |
Mar
(106) |
Apr
(77) |
May
(92) |
Jun
(63) |
Jul
(233) |
Aug
(102) |
Sep
(119) |
Oct
(63) |
Nov
(68) |
Dec
(32) |
| 2008 |
Jan
(69) |
Feb
(91) |
Mar
(129) |
Apr
(44) |
May
(18) |
Jun
(53) |
Jul
(50) |
Aug
(25) |
Sep
(11) |
Oct
(28) |
Nov
(67) |
Dec
(36) |
| 2009 |
Jan
(20) |
Feb
(24) |
Mar
(66) |
Apr
(53) |
May
(48) |
Jun
(48) |
Jul
(59) |
Aug
(82) |
Sep
(49) |
Oct
(30) |
Nov
(16) |
Dec
(16) |
| 2010 |
Jan
(52) |
Feb
(25) |
Mar
(36) |
Apr
(34) |
May
(14) |
Jun
(15) |
Jul
(14) |
Aug
(16) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(22) |
Mar
(45) |
Apr
(9) |
May
(8) |
Jun
(13) |
Jul
(12) |
Aug
(4) |
Sep
(6) |
Oct
(10) |
Nov
(21) |
Dec
(5) |
| 2012 |
Jan
(6) |
Feb
(9) |
Mar
(25) |
Apr
(6) |
May
(4) |
Jun
(23) |
Jul
(6) |
Aug
(18) |
Sep
(21) |
Oct
(34) |
Nov
(19) |
Dec
(25) |
| 2013 |
Jan
(8) |
Feb
(34) |
Mar
(35) |
Apr
(4) |
May
(11) |
Jun
(4) |
Jul
(7) |
Aug
(5) |
Sep
(20) |
Oct
(12) |
Nov
(11) |
Dec
(7) |
| 2014 |
Jan
(10) |
Feb
(18) |
Mar
(50) |
Apr
(26) |
May
(53) |
Jun
(21) |
Jul
(12) |
Aug
(39) |
Sep
(43) |
Oct
(26) |
Nov
(8) |
Dec
(6) |
| 2015 |
Jan
(18) |
Feb
(32) |
Mar
(31) |
Apr
(42) |
May
(38) |
Jun
(13) |
Jul
(6) |
Aug
(11) |
Sep
(29) |
Oct
(25) |
Nov
(10) |
Dec
(11) |
| 2016 |
Jan
(24) |
Feb
(12) |
Mar
(13) |
Apr
(15) |
May
(22) |
Jun
(8) |
Jul
(12) |
Aug
(25) |
Sep
(8) |
Oct
(6) |
Nov
(13) |
Dec
(7) |
| 2017 |
Jan
(6) |
Feb
(29) |
Mar
(32) |
Apr
(8) |
May
(82) |
Jun
(42) |
Jul
(20) |
Aug
(17) |
Sep
(27) |
Oct
(14) |
Nov
(22) |
Dec
(6) |
| 2018 |
Jan
(12) |
Feb
(9) |
Mar
(22) |
Apr
(19) |
May
(14) |
Jun
(9) |
Jul
(9) |
Aug
(22) |
Sep
(22) |
Oct
(12) |
Nov
(13) |
Dec
(8) |
| 2019 |
Jan
(22) |
Feb
(3) |
Mar
(30) |
Apr
(20) |
May
(20) |
Jun
(6) |
Jul
(15) |
Aug
(25) |
Sep
(11) |
Oct
(24) |
Nov
(11) |
Dec
(6) |
| 2020 |
Jan
(9) |
Feb
(12) |
Mar
(29) |
Apr
(10) |
May
(22) |
Jun
(11) |
Jul
(15) |
Aug
(5) |
Sep
(6) |
Oct
(7) |
Nov
(7) |
Dec
(13) |
| 2021 |
Jan
(21) |
Feb
(5) |
Mar
(5) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(6) |
Aug
(8) |
Sep
(5) |
Oct
(9) |
Nov
(5) |
Dec
(6) |
| 2022 |
Jan
(5) |
Feb
(4) |
Mar
(8) |
Apr
(6) |
May
(5) |
Jun
(5) |
Jul
(10) |
Aug
(6) |
Sep
(7) |
Oct
(4) |
Nov
(4) |
Dec
(6) |
| 2023 |
Jan
(5) |
Feb
(5) |
Mar
(6) |
Apr
(4) |
May
(5) |
Jun
(6) |
Jul
(5) |
Aug
(5) |
Sep
(5) |
Oct
(5) |
Nov
(7) |
Dec
(8) |
| 2024 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jython t. <st...@bu...> - 2017-06-02 16:10:23
|
ACTIVITY SUMMARY (2017-05-26 - 2017-06-02) 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 312 ( -1) closed 2302 ( +1) total 2614 ( +0) Open issues with patches: 28 Most recent 15 issues with no replies (15) ========================================== #2593: writing a buffer (instead of str) fails with NullPointerExcept http://bugs.jython.org/issue2593 #2591: Unable to execute directory or zip file (test_cmd_line_script) http://bugs.jython.org/issue2591 #2589: Two copies of jansi DLL created per invocation of Jython http://bugs.jython.org/issue2589 #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 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 |
|
From: Stefan R. <Ste...@gm...> - 2017-06-02 12:17:13
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div>Tobias,</div> <div>thanks for testing 2.7.1 RC2!</div> <div>I'd recommend to file this as a new issue on bugs.jython.org.</div> <div>It is better tracked there and not so likely to get lost. We can have additional discussion there.</div> <div> </div> <div>Best</div> <div> </div> <div>-Stefan</div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div style="margin:0 0 10px 0;"><b>Gesendet:</b> Donnerstag, 01. Juni 2017 um 13:00 Uhr<br/> <b>Von:</b> Tob...@dl...<br/> <b>An:</b> jyt...@li...<br/> <b>Betreff:</b> [Jython-dev] Memory leak in Jython 2.7.1 RC2?</div> <div name="quoted-content"><!--p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0.0cm; font-size: 11.0pt; font-family: Calibri , sans-serif; } a:link, span.MsoHyperlink { color: blue; text-decoration: underline; } a:visited, span.MsoHyperlinkFollowed { color: purple; text-decoration: underline; } span.E-MailFormatvorlage17 { font-family: Calibri , sans-serif; color: windowtext; } *.MsoChpDefault { font-family: Calibri , sans-serif; } div.WordSection1 { page: WordSection1; } --> <div> <div class="WordSection1"> <p class="MsoNormal"><span>Hi,</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>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.</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>One problem we encountered in an earlier Jython version (2.5.2) was the memory leak described in this bug report: <a href="http://bugs.jython.org/issue2026" target="_blank">http://bugs.jython.org/issue2026</a> . 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:</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>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.</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>I haven't created a bug report for this issue, since the RC is not officially announced, but I can do this if requested.</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>Thanks for your efforts!</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>Tobias</span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span>[0] <a href="https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l199" target="_blank">https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l199</a></span></p> <p class="MsoNormal"><span>[1] <a href="https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l1575" target="_blank">https://hg.python.org/jython/file/d4cd06b8c8c7/src/org/python/core/PySystemState.java#l1575</a></span></p> <p class="MsoNormal"><span> </span></p> <p class="MsoNormal"><span> </span></p> </div> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot_______________________________________________" target="_blank">http://sdm.link/slashdot_______________________________________________</a> Jython-dev mailing list Jyt...@li... <a href="https://lists.sourceforge.net/lists/listinfo/jython-dev" target="_blank">https://lists.sourceforge.net/lists/listinfo/jython-dev</a></div> </div> </div> </div> </div></div></body></html> |
|
From: Rory O'D. <ror...@or...> - 2017-06-02 10:22:36
|
Hi Alan, ** *Announcing: Early-Access builds of JDK 9 for Alpine Linux/musl at jdk.java.net/9/ [1] * * As of today there are pre-built Early-Access (EA) JDK binaries for Alpine Linux/musl at jdk.java.net/9/** o look for “Alpine Linux”. [1] * The Alpine Linux build is compatible with linux distributions that use the musl C library. *[2]* Feedback is very welcome via the portola-dev mailing list, remembering to subscribe to the mailing list first. *Proposed schedule change for JDK 9 [3]* JDK 9 Project continues to work toward the current goal of producing an initial Release Candidate build on 22 June. This proposal is to adjust the GA date in order to accommodate the additional time required to move through the JCP process. To be specific, we propose to move the GA date out by eight weeks, from 27 July to 21 September. Rgds,Rory [1] http://mail.openjdk.java.net/pipermail/portola-dev/2017-June/000191.html [2] http://www.musl-libc.org/ [3] http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-May/005864.html -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland |
|
From: <Tob...@dl...> - 2017-06-01 11:00:32
|
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 |
|
From: Jeff A. <ja...@fa...> - 2017-05-31 21:09:14
|
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 > |
|
From: Isaiah P. <is...@gm...> - 2017-05-31 20:30:14
|
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
>>
>
|
|
From: Jim B. <jim...@py...> - 2017-05-31 16:04:58
|
FYI - please add comments to the python-dev thread as appropriate ---------- Forwarded message ---------- From: Jim Baker <jim...@py...> Date: Wed, May 31, 2017 at 9:45 AM Subject: Re: [Python-Dev] RFC: Backport ssl.MemoryBIO and ssl.SSLObject to Python 2.7 To: Cory Benfield <co...@lu...> Cc: Victor Stinner <vic...@gm...>, Python Dev < Pyt...@py...> Jython 2.7.1 is about to be released, with full support of upstream pip (9.0.1), and corresponding vendored libraries, including requests. However, this proposed new feature for CPython 2.7, and its usage, will likely break pip on Jython 2.7.x going forward, given that future versions of pip will depend on requests requiring MemoryBIO. Or am I wrong in this analysis? This means we have to get back on the 2.7 development treadmill just as we were about to focus on finally working on Jython 3 ( https://github.com/jython/jython3 previews this work). Given that this proposed new feature is for 2.7 to support event loop usage and not a security fix, I'm -1 on this change. In particular, it runs counter to the justification policy stated in PEP 466. - Jim On Wed, May 31, 2017 at 7:25 AM, Cory Benfield <co...@lu...> wrote: > > > On 31 May 2017, at 08:42, Victor Stinner <vic...@gm...> > wrote: > > > > Hi, > > > > I wrote a PEP based on the previous thread "Backport ssl.MemoryBIO on > > Python 2.7?". Thanks for Cory Benfield, Alex Gaynor and Nick Coghlan > > who helped me to write it! > > It probably goes without saying, given that I helped with the drafting for > the PEP, but I’m strongly in favour of this PEP. Just in case it helps to > get that reaffirmation here. ;) > > Cory > > _______________________________________________ > Python-Dev mailing list > Pyt...@py... > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/jbaker% > 40zyasoft.com > |
|
From: Isaiah P. <is...@gm...> - 2017-05-31 07:57:59
|
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 > |
|
From: Jeff A. <ja...@fa...> - 2017-05-31 07:21:31
|
I found the same problems and fixed them too. And one that prevents me compiling on Windows. In the case of the "from __future__" problem I solved it differently. I will open a PR for this as a way of exercising the CPython process (see thread about that). It will conflict with the new tip, but that's ok because resolving merge conflicts is also a use case to learn. I have to do this slowly, however, with the Git Book and dev guide open! Jeff Jeff Allen On 31/05/2017 01:50, 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 > |
|
From: Jim B. <jim...@py...> - 2017-05-31 03:36:16
|
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). Then over time we can adopt CPython core workflow. 2. We should bring in the Gradle build process that Darjus is working on, and get that into Jython 3 as soon as possible. 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. On Tue, May 30, 2017 at 6:50 PM, 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 list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: <fwi...@gm...> - 2017-05-31 00:51:21
|
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 |
|
From: Jim B. <jim...@py...> - 2017-05-30 16:26:13
|
Agreed about switching our focus to Jython 3. This is the same reason why Python 3 is not backwards compatible in this way, and I'm sure the frustration of actually working with such loose typing — the never ending aspect of it — is what motivated Guido to abandon such compatibility. Time to release RC2, and hopefully this will be 2.7.1. On Tue, May 30, 2017 at 7:39 AM, Jeff Allen <ja...@fa...> wrote: > I'm happy to go with that. In the same circumstances, I believe I saw pip > on CPython 2.7 also fail, so I don't feel too bad. The ticket you link > demonstrates what I've found all through this work: beyond every line that > produces an encoding/decoding exception, there's another one just waiting > for you to reach it. > > Part of me wants to pursue it, but not as much as making Jython 3 build. > > Jeff Allen > > > On 30/05/2017 14:02, Jim Baker wrote: > >> I don't see this as a blocker for RC2 or for 2.7.1 itself: there is a >> workaround at least on Linuxes that support Unicode usernames, with jython >> -m pip. Furthermore the root problem seems to be for such installs in pip >> code, or its upstream like setuptools. Such fixes can and should be done >> outside the Jython development process. >> >> More on my reasoning: >> >> We only recently gained the capability of support Unicode in usernames, >> which incidentally is not supported on OSX (that name would have been added >> in its Pinyin form) or on RedHat. Most likely the problem is in pip and/or >> setuptools; see for example https://github.com/pypa/pip/issues/3463; the >> resolution of this requires Windows-specific code. >> >> But I can add Unicode usernames on Ubuntu 16.04.2, so I tried it with >> pip. In a nutshell, one can make it work by using jython -m pip. The >> command line version (which uses setuptools to install) fails as follows: >> >> x-耀华@thought:~$ ~/jython2.7.1-rc2/bin/pip --version >> File "<string>", line None >> SyntaxError: Non-ASCII character in file '/home/x-耀华/jython2.7.1-rc2/bin/pip', >> but no encoding declared; see http://www.python.org/peps/pep-0263.html >> for details >> >> We can workaround this with jython -m pip, and this works for packages >> that are not installing executable scripts. However, it then fails with >> something like yolk: >> >> x-耀华@thought:~$ ~/jython2.7.1-rc2/bin/jython -m pip install yolk >> Collecting yolk >> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/_vendor/req >> uests/packages/urllib3/util/ssl_.py:310: SNIMissingWarning: An HTTPS >> request has been made, but the SNI (Subject Name Indication) extension to >> TLS is not available on this platform. This may cause the server to present >> an incorrect TLS certificate, which can cause validation failures. You can >> upgrade to a newer version of Python to solve this. For more information, >> see https://urllib3.readthedocs.io/en/latest/security.html#snimi >> ssingwarning. >> warnings.warn( >> Downloading yolk-0.4.3.tar.gz (86kB) >> 100% |████████████████████████████████| 92kB 682kB/s >> Requirement already satisfied: setuptools in >> /home/x-??/jython2.7.1-rc2/Lib/site-packages (from yolk) >> Installing collected packages: yolk >> Running setup.py install for yolk ... error >> Complete output from command /home/x-耀华/jython2.7.1-rc2/bin/jython >> -u -c "import setuptools, tokenize;__file__='/tmp/pip-bu >> ild-yq3q1p/yolk/setup.py';f=getattr(tokenize, 'open', >> open)(__file__);code=f.read().replace('\r\n', >> '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record >> /tmp/pip-loUh2K-record/install-record.txt --single-version-externally-managed >> --compile: >> running install >> running build >> running build_py >> creating build >> creating build/lib >> creating build/lib/yolk >> copying yolk/cli.py -> build/lib/yolk >> copying yolk/utils.py -> build/lib/yolk >> copying yolk/pypi.py -> build/lib/yolk >> copying yolk/metadata.py -> build/lib/yolk >> copying yolk/setuptools_support.py -> build/lib/yolk >> copying yolk/yolklib.py -> build/lib/yolk >> copying yolk/__init__.py -> build/lib/yolk >> creating build/lib/yolk/plugins >> copying yolk/plugins/__init__.py -> build/lib/yolk/plugins >> copying yolk/plugins/base.py -> build/lib/yolk/plugins >> running install_lib >> creating /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk >> copying build/lib/yolk/cli.py -> /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk >> copying build/lib/yolk/utils.py -> /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk >> copying build/lib/yolk/pypi.py -> /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk >> copying build/lib/yolk/metadata.py -> /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk >> copying build/lib/yolk/setuptools_support.py -> >> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk >> copying build/lib/yolk/yolklib.py -> /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk >> creating /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins >> copying build/lib/yolk/plugins/__init__.py -> >> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins >> copying build/lib/yolk/plugins/base.py -> >> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins >> copying build/lib/yolk/__init__.py -> /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/cli.py >> to cli$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/utils.py >> to utils$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/pypi.py >> to pypi$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk/metadata.py to metadata$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk/setuptools_support.py to setuptools_support$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/yolklib.py >> to yolklib$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk/plugins/__init__.py to __init__$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk/plugins/base.py to base$py.class >> byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk/__init__.py to __init__$py.class >> running install_egg_info >> running egg_info >> writing yolk.egg-info/PKG-INFO >> writing requirements to yolk.egg-info/requires.txt >> writing entry points to yolk.egg-info/entry_points.txt >> writing top-level names to yolk.egg-info/top_level.txt >> writing dependency_links to yolk.egg-info/dependency_links.txt >> warning: manifest_maker: standard file '-c' not found >> >> reading manifest file 'yolk.egg-info/SOURCES.txt' >> reading manifest template 'MANIFEST.in' >> warning: no files found matching '*.txt' under directory 'tests' >> warning: no files found matching '*.conf' under directory 'docs' >> warning: no files found matching '*.css_t' under directory 'docs' >> warning: no files found matching 'indexsidebar.html' under directory >> 'docs' >> warning: no files found matching 'tests/test_cli.py' >> writing manifest file 'yolk.egg-info/SOURCES.txt' >> Copying yolk.egg-info to /home/x-耀华/jython2.7.1-rc2/Lib >> /site-packages/yolk-0.4.3-py2.7.egg-info >> running install_scripts >> Installing yolk script to /home/x-耀华/jython2.7.1-rc2/bin >> Traceback (most recent call last): >> File "<string>", line 1, in <module> >> File "/tmp/pip-build-yq3q1p/yolk/setup.py", line 10, in <module> >> setup(name="yolk", >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/core.py", line 151, >> in setup >> dist.run_commands() >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/core.py", line 151, >> in setup >> dist.run_commands() >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line 953, >> in run_commands >> self.run_command(cmd) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line 972, >> in run_command >> cmd_obj.run() >> File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install.py", >> line 61, in run >> return orig.install.run(self) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/command/install.py", >> line 589, in run >> self.run_command(cmd_name) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/cmd.py", line 326, >> in run_command >> self.distribution.run_command(command) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line 972, >> in run_command >> cmd_obj.run() >> File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install_scripts.py", >> line 49, in run >> self.write_script(*args) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install_scripts.py", >> line 63, in write_script >> f.write(contents) >> UnicodeEncodeError: 'ascii' codec can't encode characters in position >> 10-11: ordinal not in range(128) >> >> ---------------------------------------- >> Traceback (most recent call last): >> File "/home/x-耀华/jython2.7.1-rc2/Lib/runpy.py", line 161, in >> _run_module_as_main >> return _run_code(code, main_globals, None, >> File "/home/x-耀华/jython2.7.1-rc2/Lib/runpy.py", line 72, in _run_code >> exec code in run_globals >> File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/__main__.py", >> line 19, in <module> >> sys.exit(pip.main()) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/__init__.py", >> line 233, in main >> return command.main(cmd_args) >> File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/basecommand.py", >> line 226, in main >> logger.critical(str(exc)) >> UnicodeEncodeError: 'ascii' codec can't encode characters in position >> 17-18: ordinal not in range(128) >> >> >> On Tue, May 30, 2017 at 1:45 AM, Jeff Allen <ja...@fa... <mailto: >> ja...@fa...>> wrote: >> >> I have also tested installing yolk. >> >> This works on Windows for my account, but not for user 用户名, where >> pip fails while trying to do an os.path.join(). I've traced this >> back to the fact that the URL that it derived the filename from is >> a unicode, whereas the base directory for installation is a >> byte-encoded non-ascii path. I blame the derivation of the url, >> but I haven't found where its unicode-ness first arises. I suspect >> it is on return from a Java method we use/wrote in urllib*. >> >> How seriously do we rate this? >> >> Jeff Allen >> >> On 30/05/2017 02:46, Jim Baker wrote: >> >>> I also tested the installer on Ubuntu 16.04.2 LTS with Java 8 >>> (1.8.0_131), and it works as expected (regrtest, yolk smoke >>> test); I also tested the standalone jar. More below. >>> >>> Given Jeff's testing on Windows — very nice that Jython now works >>> with Unicode in the username! — we have completed basic sanity >>> checks and *we can finalize this RC2*. >>> >>> I haven't really tried to do much testing with the standalone jar >>> in the past, in part because all the tests are stripped from it. >>> However, it is possible to run most of the tests, excluding >>> introspective type tests that try to look up Python files that >>> are enclosed in the standalone jar (not going to work before we >>> fix http://bugs.jython.org/issue2143 >>> <http://bugs.jython.org/issue2143>). >>> >>> Also interestingly it is possible to do the following with the >>> standalone jar: >>> >>> $ java -jar jython-standalone-2.7.1-rc2.jar -m ensurepip >>> Collecting setuptools >>> Collecting pip >>> Installing collected packages: setuptools, pip >>> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >>> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >>> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >>> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >>> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >>> Successfully installed pip-9.0.1 setuptools-28.8.0 >>> jimbaker:test-standalone jbaker$ java -jar >>> jython-standalone-2.7.1-rc2.jar -m pip install pytz >>> Collecting pytz >>> Downloading pytz-2017.2-py2.py3-none-any.whl (484kB) >>> 100% |████████████████████████████████| 491kB 556kB/s >>> Installing collected packages: pytz >>> Successfully installed pytz-2017.2 >>> >>> And then use the pytz package etc. Such packages are simply >>> installed in Lib/site-packages, which will be created if missing. >>> JYTHONPATH probably needs to be set properly for all this to >>> work. Interesting detail that I hadn't connected before myself. >>> >>> On Mon, May 29, 2017 at 7:27 PM, Jim Baker <jim...@py... >>> <mailto:jim...@py...>> wrote: >>> >>> I tested the installation on OSX 10.12 (Sierra), including >>> the smoke test for pip/setuptools (yolk) and the regrtest, >>> and it works as expected. >>> >>> As I mentioned in http://bugs.jython.org/issue2594 >>> <http://bugs.jython.org/issue2594>, test_load_cert_chain in >>> test_ssl relies on signed jars in Bouncy Castle. Fortunately >>> if those jars are on the CLASSPATH, they will precede >>> Jython's shaded/uber jar variants. >>> >>> >>> >>> On Mon, May 29, 2017 at 6:25 PM, Jeff Allen >>> <ja...@fa... <mailto:ja...@fa...>> wrote: >>> >>> This installed fine for me on Windows (actually for user >>> 用户名), including pip & setuptools. >>> >>> I ran the regression test as ..\2.7.1-rc2\bin\jython -m >>> test.regrtest -e and got 3 failures. >>> >>> 372 tests OK. >>> 7 tests skipped: >>> test_codecmaps_hk test_curses test_smtpnet >>> test_socketserver >>> test_subprocess test_urllib2net test_urllibnet >>> 3 tests failed: >>> test___all__ test_inspect test_ssl >>> 3 fails unexpected: >>> test___all__ test_inspect test_ssl >>> >>> test___all__ fails on a missing ServeletException see >>> http://bugs.jython.org/issue2308 >>> <http://bugs.jython.org/issue2308> >>> >>> ..\2.7.1-rc2\bin\jython -m test.test_inspect >>> ..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect >>> pass when re-run in isolation. >>> >>> ..\2.7.1-rc2\bin\jython -m test.test_ssl >>> fails as reported in http://bugs.jython.org/issue2594 >>> <http://bugs.jython.org/issue2594> >>> >>> Passing test with Netty shower: >>> >>> test_socket >>> May 29, 2017 8:28:36 PM >>> org.python.netty.bootstrap.AbstractBootstrap >>> setChannelOption >>> WARNING: Unknown channel option 'SO_KEEPALIVE' for >>> channel '[id: 0x286e32d1]' >>> May 29, 2017 8:28:36 PM >>> org.python.netty.bootstrap.AbstractBootstrap >>> setChannelOption >>> WARNING: Unknown channel option 'SO_KEEPALIVE' for >>> channel '[id: 0x666fcd99]' >>> May 29, 2017 8:28:40 PM >>> org.python.netty.util.concurrent.DefaultPromise safeExecute >>> SEVERE: Failed to submit a listener notification task. >>> Event loop shut down? >>> java.util.concurrent.RejectedExecutionException: event >>> executor terminated >>> at >>> org.python.netty.util.concurrent.SingleThreadEventExecutor.r >>> eject(SingleThreadEventExecutor.java:821) >>> at >>> org.python.netty.util.concurrent.SingleThreadEventExecutor.o >>> fferTask(SingleThreadEventExecutor.java:327) >>> at >>> org.python.netty.util.concurrent.SingleThreadEventExecutor.a >>> ddTask(SingleThreadEventExecutor.java:320) >>> ... >>> >>> Maybe the SSL failure is a worry, but nothing else. >>> >>> Jeff >>> >>> >>> Jeff Allen >>> >>> >>> On 29/05/2017 19:17, fwi...@gm... >>> <mailto:fwi...@gm...> 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- >>> 1065/org/python/jython-installer/2.7.1-rc2/jython- >>> installer-2.7.1-rc2.jar >>> <https://oss.sonatype.org/cont >>> ent/repositories/orgpython-1065/org/python/jython- >>> installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar> >>> >>> standalone: >>> https://oss.sonatype.org/content/repositories/orgpython- >>> 1066/org/python/jython-standalone/2.7.1-rc2/jython- >>> standalone-2.7.1-rc2.jar >>> <https://oss.sonatype.org/cont >>> ent/repositories/orgpython-1066/org/python/jython- >>> standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.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 >>> Jyt...@li... >>> <mailto:Jyt...@li...> >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> <https://lists.sourceforge.net/lists/listinfo/jython-dev >>> > >>> >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the >>> world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> <mailto:Jyt...@li...> >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> <https://lists.sourceforge.net/lists/listinfo/jython-dev> >>> >>> >>> >>> >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Jeff A. <ja...@fa...> - 2017-05-30 13:39:59
|
I'm happy to go with that. In the same circumstances, I believe I saw pip on CPython 2.7 also fail, so I don't feel too bad. The ticket you link demonstrates what I've found all through this work: beyond every line that produces an encoding/decoding exception, there's another one just waiting for you to reach it. Part of me wants to pursue it, but not as much as making Jython 3 build. Jeff Allen On 30/05/2017 14:02, Jim Baker wrote: > I don't see this as a blocker for RC2 or for 2.7.1 itself: there is a > workaround at least on Linuxes that support Unicode usernames, with > jython -m pip. Furthermore the root problem seems to be for such > installs in pip code, or its upstream like setuptools. Such fixes can > and should be done outside the Jython development process. > > More on my reasoning: > > We only recently gained the capability of support Unicode in > usernames, which incidentally is not supported on OSX (that name would > have been added in its Pinyin form) or on RedHat. Most likely the > problem is in pip and/or setuptools; see for example > https://github.com/pypa/pip/issues/3463; the resolution of this > requires Windows-specific code. > > But I can add Unicode usernames on Ubuntu 16.04.2, so I tried it with > pip. In a nutshell, one can make it work by using jython -m pip. The > command line version (which uses setuptools to install) fails as follows: > > x-耀华@thought:~$ ~/jython2.7.1-rc2/bin/pip --version > File "<string>", line None > SyntaxError: Non-ASCII character in file > '/home/x-耀华/jython2.7.1-rc2/bin/pip', but no encoding declared; see > http://www.python.org/peps/pep-0263.html for details > > We can workaround this with jython -m pip, and this works for packages > that are not installing executable scripts. However, it then fails > with something like yolk: > > x-耀华@thought:~$ ~/jython2.7.1-rc2/bin/jython -m pip install yolk > Collecting yolk > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:310: > SNIMissingWarning: An HTTPS request has been made, but the SNI > (Subject Name Indication) extension to TLS is not available on this > platform. This may cause the server to present an incorrect TLS > certificate, which can cause validation failures. You can upgrade to a > newer version of Python to solve this. For more information, see > https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning. > warnings.warn( > Downloading yolk-0.4.3.tar.gz (86kB) > 100% |████████████████████████████████| 92kB 682kB/s > Requirement already satisfied: setuptools in > /home/x-??/jython2.7.1-rc2/Lib/site-packages (from yolk) > Installing collected packages: yolk > Running setup.py install for yolk ... error > Complete output from command /home/x-耀华/jython2.7.1-rc2/bin/jython > -u -c "import setuptools, > tokenize;__file__='/tmp/pip-build-yq3q1p/yolk/setup.py';f=getattr(tokenize, > 'open', open)(__file__);code=f.read().replace('\r\n', > '\n');f.close();exec(compile(code, __file__, 'exec'))" install > --record /tmp/pip-loUh2K-record/install-record.txt > --single-version-externally-managed --compile: > running install > running build > running build_py > creating build > creating build/lib > creating build/lib/yolk > copying yolk/cli.py -> build/lib/yolk > copying yolk/utils.py -> build/lib/yolk > copying yolk/pypi.py -> build/lib/yolk > copying yolk/metadata.py -> build/lib/yolk > copying yolk/setuptools_support.py -> build/lib/yolk > copying yolk/yolklib.py -> build/lib/yolk > copying yolk/__init__.py -> build/lib/yolk > creating build/lib/yolk/plugins > copying yolk/plugins/__init__.py -> build/lib/yolk/plugins > copying yolk/plugins/base.py -> build/lib/yolk/plugins > running install_lib > creating /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > copying build/lib/yolk/cli.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > copying build/lib/yolk/utils.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > copying build/lib/yolk/pypi.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > copying build/lib/yolk/metadata.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > copying build/lib/yolk/setuptools_support.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > copying build/lib/yolk/yolklib.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > creating /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins > copying build/lib/yolk/plugins/__init__.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins > copying build/lib/yolk/plugins/base.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins > copying build/lib/yolk/__init__.py -> > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/cli.py to cli$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/utils.py to > utils$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/pypi.py to > pypi$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/metadata.py to > metadata$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/setuptools_support.py > to setuptools_support$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/yolklib.py to > yolklib$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins/__init__.py > to __init__$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins/base.py to > base$py.class > byte-compiling > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/__init__.py to > __init__$py.class > running install_egg_info > running egg_info > writing yolk.egg-info/PKG-INFO > writing requirements to yolk.egg-info/requires.txt > writing entry points to yolk.egg-info/entry_points.txt > writing top-level names to yolk.egg-info/top_level.txt > writing dependency_links to yolk.egg-info/dependency_links.txt > warning: manifest_maker: standard file '-c' not found > > reading manifest file 'yolk.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching '*.txt' under directory 'tests' > warning: no files found matching '*.conf' under directory 'docs' > warning: no files found matching '*.css_t' under directory 'docs' > warning: no files found matching 'indexsidebar.html' under > directory 'docs' > warning: no files found matching 'tests/test_cli.py' > writing manifest file 'yolk.egg-info/SOURCES.txt' > Copying yolk.egg-info to > /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk-0.4.3-py2.7.egg-info > running install_scripts > Installing yolk script to /home/x-耀华/jython2.7.1-rc2/bin > Traceback (most recent call last): > File "<string>", line 1, in <module> > File "/tmp/pip-build-yq3q1p/yolk/setup.py", line 10, in <module> > setup(name="yolk", > File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/core.py", line > 151, in setup > dist.run_commands() > File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/core.py", line > 151, in setup > dist.run_commands() > File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line > 953, in run_commands > self.run_command(cmd) > File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line > 972, in run_command > cmd_obj.run() > File > "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install.py", > line 61, in run > return orig.install.run(self) > File > "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/command/install.py", line > 589, in run > self.run_command(cmd_name) > File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/cmd.py", line > 326, in run_command > self.distribution.run_command(command) > File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line > 972, in run_command > cmd_obj.run() > File > "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install_scripts.py", > line 49, in run > self.write_script(*args) > File > "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install_scripts.py", > line 63, in write_script > f.write(contents) > UnicodeEncodeError: 'ascii' codec can't encode characters in > position 10-11: ordinal not in range(128) > > ---------------------------------------- > Traceback (most recent call last): > File "/home/x-耀华/jython2.7.1-rc2/Lib/runpy.py", line 161, in > _run_module_as_main > return _run_code(code, main_globals, None, > File "/home/x-耀华/jython2.7.1-rc2/Lib/runpy.py", line 72, in _run_code > exec code in run_globals > File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/__main__.py", > line 19, in <module> > sys.exit(pip.main()) > File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/__init__.py", > line 233, in main > return command.main(cmd_args) > File > "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/basecommand.py", > line 226, in main > logger.critical(str(exc)) > UnicodeEncodeError: 'ascii' codec can't encode characters in position > 17-18: ordinal not in range(128) > > > On Tue, May 30, 2017 at 1:45 AM, Jeff Allen <ja...@fa... > <mailto:ja...@fa...>> wrote: > > I have also tested installing yolk. > > This works on Windows for my account, but not for user 用户名, where > pip fails while trying to do an os.path.join(). I've traced this > back to the fact that the URL that it derived the filename from is > a unicode, whereas the base directory for installation is a > byte-encoded non-ascii path. I blame the derivation of the url, > but I haven't found where its unicode-ness first arises. I suspect > it is on return from a Java method we use/wrote in urllib*. > > How seriously do we rate this? > > Jeff Allen > > On 30/05/2017 02:46, Jim Baker wrote: >> I also tested the installer on Ubuntu 16.04.2 LTS with Java 8 >> (1.8.0_131), and it works as expected (regrtest, yolk smoke >> test); I also tested the standalone jar. More below. >> >> Given Jeff's testing on Windows — very nice that Jython now works >> with Unicode in the username! — we have completed basic sanity >> checks and *we can finalize this RC2*. >> >> I haven't really tried to do much testing with the standalone jar >> in the past, in part because all the tests are stripped from it. >> However, it is possible to run most of the tests, excluding >> introspective type tests that try to look up Python files that >> are enclosed in the standalone jar (not going to work before we >> fix http://bugs.jython.org/issue2143 >> <http://bugs.jython.org/issue2143>). >> >> Also interestingly it is possible to do the following with the >> standalone jar: >> >> $ java -jar jython-standalone-2.7.1-rc2.jar -m ensurepip >> Collecting setuptools >> Collecting pip >> Installing collected packages: setuptools, pip >> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >> Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython >> Successfully installed pip-9.0.1 setuptools-28.8.0 >> jimbaker:test-standalone jbaker$ java -jar >> jython-standalone-2.7.1-rc2.jar -m pip install pytz >> Collecting pytz >> Downloading pytz-2017.2-py2.py3-none-any.whl (484kB) >> 100% |████████████████████████████████| 491kB 556kB/s >> Installing collected packages: pytz >> Successfully installed pytz-2017.2 >> >> And then use the pytz package etc. Such packages are simply >> installed in Lib/site-packages, which will be created if missing. >> JYTHONPATH probably needs to be set properly for all this to >> work. Interesting detail that I hadn't connected before myself. >> >> On Mon, May 29, 2017 at 7:27 PM, Jim Baker <jim...@py... >> <mailto:jim...@py...>> wrote: >> >> I tested the installation on OSX 10.12 (Sierra), including >> the smoke test for pip/setuptools (yolk) and the regrtest, >> and it works as expected. >> >> As I mentioned in http://bugs.jython.org/issue2594 >> <http://bugs.jython.org/issue2594>, test_load_cert_chain in >> test_ssl relies on signed jars in Bouncy Castle. Fortunately >> if those jars are on the CLASSPATH, they will precede >> Jython's shaded/uber jar variants. >> >> >> >> On Mon, May 29, 2017 at 6:25 PM, Jeff Allen >> <ja...@fa... <mailto:ja...@fa...>> wrote: >> >> This installed fine for me on Windows (actually for user >> 用户名), including pip & setuptools. >> >> I ran the regression test as ..\2.7.1-rc2\bin\jython -m >> test.regrtest -e and got 3 failures. >> >> 372 tests OK. >> 7 tests skipped: >> test_codecmaps_hk test_curses test_smtpnet >> test_socketserver >> test_subprocess test_urllib2net test_urllibnet >> 3 tests failed: >> test___all__ test_inspect test_ssl >> 3 fails unexpected: >> test___all__ test_inspect test_ssl >> >> test___all__ fails on a missing ServeletException see >> http://bugs.jython.org/issue2308 >> <http://bugs.jython.org/issue2308> >> >> ..\2.7.1-rc2\bin\jython -m test.test_inspect >> ..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect >> pass when re-run in isolation. >> >> ..\2.7.1-rc2\bin\jython -m test.test_ssl >> fails as reported in http://bugs.jython.org/issue2594 >> <http://bugs.jython.org/issue2594> >> >> Passing test with Netty shower: >> >> test_socket >> May 29, 2017 8:28:36 PM >> org.python.netty.bootstrap.AbstractBootstrap setChannelOption >> WARNING: Unknown channel option 'SO_KEEPALIVE' for >> channel '[id: 0x286e32d1]' >> May 29, 2017 8:28:36 PM >> org.python.netty.bootstrap.AbstractBootstrap setChannelOption >> WARNING: Unknown channel option 'SO_KEEPALIVE' for >> channel '[id: 0x666fcd99]' >> May 29, 2017 8:28:40 PM >> org.python.netty.util.concurrent.DefaultPromise safeExecute >> SEVERE: Failed to submit a listener notification task. >> Event loop shut down? >> java.util.concurrent.RejectedExecutionException: event >> executor terminated >> at >> org.python.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:821) >> at >> org.python.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:327) >> at >> org.python.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:320) >> ... >> >> Maybe the SSL failure is a worry, but nothing else. >> >> Jeff >> >> >> Jeff Allen >> >> >> On 29/05/2017 19:17, fwi...@gm... >> <mailto:fwi...@gm...> 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-1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar >> <https://oss.sonatype.org/content/repositories/orgpython-1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar> >> >> standalone: >> https://oss.sonatype.org/content/repositories/orgpython-1066/org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.jar >> <https://oss.sonatype.org/content/repositories/orgpython-1066/org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.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 >> Jyt...@li... >> <mailto:Jyt...@li...> >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> <https://lists.sourceforge.net/lists/listinfo/jython-dev> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the >> world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> <mailto:Jyt...@li...> >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> <https://lists.sourceforge.net/lists/listinfo/jython-dev> >> >> >> > > |
|
From: Jim B. <jim...@py...> - 2017-05-30 13:03:18
|
I don't see this as a blocker for RC2 or for 2.7.1 itself: there is a workaround at least on Linuxes that support Unicode usernames, with jython -m pip. Furthermore the root problem seems to be for such installs in pip code, or its upstream like setuptools. Such fixes can and should be done outside the Jython development process. More on my reasoning: We only recently gained the capability of support Unicode in usernames, which incidentally is not supported on OSX (that name would have been added in its Pinyin form) or on RedHat. Most likely the problem is in pip and/or setuptools; see for example https://github.com/pypa/pip/issues/3463; the resolution of this requires Windows-specific code. But I can add Unicode usernames on Ubuntu 16.04.2, so I tried it with pip. In a nutshell, one can make it work by using jython -m pip. The command line version (which uses setuptools to install) fails as follows: x-耀华@thought:~$ ~/jython2.7.1-rc2/bin/pip --version File "<string>", line None SyntaxError: Non-ASCII character in file '/home/x-耀华/jython2.7.1-rc2/bin/pip', but no encoding declared; see http://www.python.org/peps/pep-0263.html for details We can workaround this with jython -m pip, and this works for packages that are not installing executable scripts. However, it then fails with something like yolk: x-耀华@thought:~$ ~/jython2.7.1-rc2/bin/jython -m pip install yolk Collecting yolk /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:310: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/security.html#snimissingwarning. warnings.warn( Downloading yolk-0.4.3.tar.gz (86kB) 100% |████████████████████████████████| 92kB 682kB/s Requirement already satisfied: setuptools in /home/x-??/jython2.7.1-rc2/Lib/site-packages (from yolk) Installing collected packages: yolk Running setup.py install for yolk ... error Complete output from command /home/x-耀华/jython2.7.1-rc2/bin/jython -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-yq3q1p/yolk/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-loUh2K-record/install-record.txt --single-version-externally-managed --compile: running install running build running build_py creating build creating build/lib creating build/lib/yolk copying yolk/cli.py -> build/lib/yolk copying yolk/utils.py -> build/lib/yolk copying yolk/pypi.py -> build/lib/yolk copying yolk/metadata.py -> build/lib/yolk copying yolk/setuptools_support.py -> build/lib/yolk copying yolk/yolklib.py -> build/lib/yolk copying yolk/__init__.py -> build/lib/yolk creating build/lib/yolk/plugins copying yolk/plugins/__init__.py -> build/lib/yolk/plugins copying yolk/plugins/base.py -> build/lib/yolk/plugins running install_lib creating /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk copying build/lib/yolk/cli.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk copying build/lib/yolk/utils.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk copying build/lib/yolk/pypi.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk copying build/lib/yolk/metadata.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk copying build/lib/yolk/setuptools_support.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk copying build/lib/yolk/yolklib.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk creating /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins copying build/lib/yolk/plugins/__init__.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins copying build/lib/yolk/plugins/base.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins copying build/lib/yolk/__init__.py -> /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/cli.py to cli$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/utils.py to utils$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/pypi.py to pypi$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/metadata.py to metadata$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/setuptools_support.py to setuptools_support$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/yolklib.py to yolklib$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins/__init__.py to __init__$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/plugins/base.py to base$py.class byte-compiling /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk/__init__.py to __init__$py.class running install_egg_info running egg_info writing yolk.egg-info/PKG-INFO writing requirements to yolk.egg-info/requires.txt writing entry points to yolk.egg-info/entry_points.txt writing top-level names to yolk.egg-info/top_level.txt writing dependency_links to yolk.egg-info/dependency_links.txt warning: manifest_maker: standard file '-c' not found reading manifest file 'yolk.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.txt' under directory 'tests' warning: no files found matching '*.conf' under directory 'docs' warning: no files found matching '*.css_t' under directory 'docs' warning: no files found matching 'indexsidebar.html' under directory 'docs' warning: no files found matching 'tests/test_cli.py' writing manifest file 'yolk.egg-info/SOURCES.txt' Copying yolk.egg-info to /home/x-耀华/jython2.7.1-rc2/Lib/site-packages/yolk-0.4.3-py2.7.egg-info running install_scripts Installing yolk script to /home/x-耀华/jython2.7.1-rc2/bin Traceback (most recent call last): File "<string>", line 1, in <module> File "/tmp/pip-build-yq3q1p/yolk/setup.py", line 10, in <module> setup(name="yolk", File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/core.py", line 151, in setup dist.run_commands() File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/core.py", line 151, in setup dist.run_commands() File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install.py", line 61, in run return orig.install.run(self) File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/command/install.py", line 589, in run self.run_command(cmd_name) File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/cmd.py", line 326, in run_command self.distribution.run_command(command) File "/home/x-耀华/jython2.7.1-rc2/Lib/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install_scripts.py", line 49, in run self.write_script(*args) File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/setuptools/command/install_scripts.py", line 63, in write_script f.write(contents) UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-11: ordinal not in range(128) ---------------------------------------- Traceback (most recent call last): File "/home/x-耀华/jython2.7.1-rc2/Lib/runpy.py", line 161, in _run_module_as_main return _run_code(code, main_globals, None, File "/home/x-耀华/jython2.7.1-rc2/Lib/runpy.py", line 72, in _run_code exec code in run_globals File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/__main__.py", line 19, in <module> sys.exit(pip.main()) File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/__init__.py", line 233, in main return command.main(cmd_args) File "/home/x-耀华/jython2.7.1-rc2/Lib/site-packages/pip/basecommand.py", line 226, in main logger.critical(str(exc)) UnicodeEncodeError: 'ascii' codec can't encode characters in position 17-18: ordinal not in range(128) On Tue, May 30, 2017 at 1:45 AM, Jeff Allen <ja...@fa...> wrote: > I have also tested installing yolk. > > This works on Windows for my account, but not for user 用户名, where pip > fails while trying to do an os.path.join(). I've traced this back to the > fact that the URL that it derived the filename from is a unicode, whereas > the base directory for installation is a byte-encoded non-ascii path. I > blame the derivation of the url, but I haven't found where its unicode-ness > first arises. I suspect it is on return from a Java method we use/wrote in > urllib*. > > How seriously do we rate this? > > Jeff Allen > > On 30/05/2017 02:46, Jim Baker wrote: > > I also tested the installer on Ubuntu 16.04.2 LTS with Java 8 (1.8.0_131), > and it works as expected (regrtest, yolk smoke test); I also tested the > standalone jar. More below. > > Given Jeff's testing on Windows — very nice that Jython now works with > Unicode in the username! — we have completed basic sanity checks and *we > can finalize this RC2*. > > I haven't really tried to do much testing with the standalone jar in the > past, in part because all the tests are stripped from it. However, it is > possible to run most of the tests, excluding introspective type tests that > try to look up Python files that are enclosed in the standalone jar (not > going to work before we fix http://bugs.jython.org/issue2143). > > Also interestingly it is possible to do the following with the standalone > jar: > > $ java -jar jython-standalone-2.7.1-rc2.jar -m ensurepip > Collecting setuptools > Collecting pip > Installing collected packages: setuptools, pip > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Successfully installed pip-9.0.1 setuptools-28.8.0 > jimbaker:test-standalone jbaker$ java -jar jython-standalone-2.7.1-rc2.jar > -m pip install pytz > Collecting pytz > Downloading pytz-2017.2-py2.py3-none-any.whl (484kB) > 100% |████████████████████████████████| 491kB 556kB/s > Installing collected packages: pytz > Successfully installed pytz-2017.2 > > And then use the pytz package etc. Such packages are simply installed in > Lib/site-packages, which will be created if missing. JYTHONPATH probably > needs to be set properly for all this to work. Interesting detail that I > hadn't connected before myself. > > On Mon, May 29, 2017 at 7:27 PM, Jim Baker <jim...@py...> wrote: > >> I tested the installation on OSX 10.12 (Sierra), including the smoke test >> for pip/setuptools (yolk) and the regrtest, and it works as expected. >> >> As I mentioned in http://bugs.jython.org/issue2594, test_load_cert_chain >> in test_ssl relies on signed jars in Bouncy Castle. Fortunately if those >> jars are on the CLASSPATH, they will precede Jython's shaded/uber jar >> variants. >> >> >> >> On Mon, May 29, 2017 at 6:25 PM, Jeff Allen <ja...@fa...> wrote: >> >>> This installed fine for me on Windows (actually for user 用户名), including >>> pip & setuptools. >>> >>> I ran the regression test as ..\2.7.1-rc2\bin\jython -m test.regrtest -e >>> and got 3 failures. >>> >>> 372 tests OK. >>> 7 tests skipped: >>> test_codecmaps_hk test_curses test_smtpnet test_socketserver >>> test_subprocess test_urllib2net test_urllibnet >>> 3 tests failed: >>> test___all__ test_inspect test_ssl >>> 3 fails unexpected: >>> test___all__ test_inspect test_ssl >>> >>> test___all__ fails on a missing ServeletException see >>> http://bugs.jython.org/issue2308 >>> >>> ..\2.7.1-rc2\bin\jython -m test.test_inspect >>> ..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect >>> pass when re-run in isolation. >>> >>> ..\2.7.1-rc2\bin\jython -m test.test_ssl >>> fails as reported in http://bugs.jython.org/issue2594 >>> >>> Passing test with Netty shower: >>> >>> test_socket >>> May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap >>> setChannelOption >>> WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id: >>> 0x286e32d1]' >>> May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap >>> setChannelOption >>> WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id: >>> 0x666fcd99]' >>> May 29, 2017 8:28:40 PM org.python.netty.util.concurrent.DefaultPromise >>> safeExecute >>> SEVERE: Failed to submit a listener notification task. Event loop shut >>> down? >>> java.util.concurrent.RejectedExecutionException: event executor >>> terminated >>> at org.python.netty.util.concurrent.SingleThreadEventExecutor.r >>> eject(SingleThreadEventExecutor.java:821) >>> at org.python.netty.util.concurrent.SingleThreadEventExecutor.o >>> fferTask(SingleThreadEventExecutor.java:327) >>> at org.python.netty.util.concurrent.SingleThreadEventExecutor.a >>> ddTask(SingleThreadEventExecutor.java:320) >>> ... >>> >>> Maybe the SSL failure is a worry, but nothing else. >>> >>> Jeff >>> >>> >>> Jeff Allen >>> >>> >>> On 29/05/2017 19:17, fwi...@gm... 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-1065 >>>> /org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar >>>> >>>> standalone: https://oss.sonatype.org/conte >>>> nt/repositories/orgpython-1066/org/python/jython-standalone/ >>>> 2.7.1-rc2/jython-standalone-2.7.1-rc2.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 >>>> Jyt...@li... >>>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>>> >>>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >> >> > > |
|
From: Jeff A. <ja...@fa...> - 2017-05-30 07:46:06
|
I have also tested installing yolk. This works on Windows for my account, but not for user 用户名, where pip fails while trying to do an os.path.join(). I've traced this back to the fact that the URL that it derived the filename from is a unicode, whereas the base directory for installation is a byte-encoded non-ascii path. I blame the derivation of the url, but I haven't found where its unicode-ness first arises. I suspect it is on return from a Java method we use/wrote in urllib*. How seriously do we rate this? Jeff Allen On 30/05/2017 02:46, Jim Baker wrote: > I also tested the installer on Ubuntu 16.04.2 LTS with Java 8 > (1.8.0_131), and it works as expected (regrtest, yolk smoke test); I > also tested the standalone jar. More below. > > Given Jeff's testing on Windows — very nice that Jython now works with > Unicode in the username! — we have completed basic sanity checks and > *we can finalize this RC2*. > > I haven't really tried to do much testing with the standalone jar in > the past, in part because all the tests are stripped from it. However, > it is possible to run most of the tests, excluding introspective type > tests that try to look up Python files that are enclosed in the > standalone jar (not going to work before we fix > http://bugs.jython.org/issue2143). > > Also interestingly it is possible to do the following with the > standalone jar: > > $ java -jar jython-standalone-2.7.1-rc2.jar -m ensurepip > Collecting setuptools > Collecting pip > Installing collected packages: setuptools, pip > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython > Successfully installed pip-9.0.1 setuptools-28.8.0 > jimbaker:test-standalone jbaker$ java -jar > jython-standalone-2.7.1-rc2.jar -m pip install pytz > Collecting pytz > Downloading pytz-2017.2-py2.py3-none-any.whl (484kB) > 100% |████████████████████████████████| 491kB 556kB/s > Installing collected packages: pytz > Successfully installed pytz-2017.2 > > And then use the pytz package etc. Such packages are simply installed > in Lib/site-packages, which will be created if missing. JYTHONPATH > probably needs to be set properly for all this to work. Interesting > detail that I hadn't connected before myself. > > On Mon, May 29, 2017 at 7:27 PM, Jim Baker <jim...@py... > <mailto:jim...@py...>> wrote: > > I tested the installation on OSX 10.12 (Sierra), including the > smoke test for pip/setuptools (yolk) and the regrtest, and it > works as expected. > > As I mentioned in http://bugs.jython.org/issue2594 > <http://bugs.jython.org/issue2594>, test_load_cert_chain in > test_ssl relies on signed jars in Bouncy Castle. Fortunately if > those jars are on the CLASSPATH, they will precede Jython's > shaded/uber jar variants. > > > > On Mon, May 29, 2017 at 6:25 PM, Jeff Allen <ja...@fa... > <mailto:ja...@fa...>> wrote: > > This installed fine for me on Windows (actually for user 用户名), > including pip & setuptools. > > I ran the regression test as ..\2.7.1-rc2\bin\jython -m > test.regrtest -e and got 3 failures. > > 372 tests OK. > 7 tests skipped: > test_codecmaps_hk test_curses test_smtpnet test_socketserver > test_subprocess test_urllib2net test_urllibnet > 3 tests failed: > test___all__ test_inspect test_ssl > 3 fails unexpected: > test___all__ test_inspect test_ssl > > test___all__ fails on a missing ServeletException see > http://bugs.jython.org/issue2308 > <http://bugs.jython.org/issue2308> > > ..\2.7.1-rc2\bin\jython -m test.test_inspect > ..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect > pass when re-run in isolation. > > ..\2.7.1-rc2\bin\jython -m test.test_ssl > fails as reported in http://bugs.jython.org/issue2594 > <http://bugs.jython.org/issue2594> > > Passing test with Netty shower: > > test_socket > May 29, 2017 8:28:36 PM > org.python.netty.bootstrap.AbstractBootstrap setChannelOption > WARNING: Unknown channel option 'SO_KEEPALIVE' for channel > '[id: 0x286e32d1]' > May 29, 2017 8:28:36 PM > org.python.netty.bootstrap.AbstractBootstrap setChannelOption > WARNING: Unknown channel option 'SO_KEEPALIVE' for channel > '[id: 0x666fcd99]' > May 29, 2017 8:28:40 PM > org.python.netty.util.concurrent.DefaultPromise safeExecute > SEVERE: Failed to submit a listener notification task. Event > loop shut down? > java.util.concurrent.RejectedExecutionException: event > executor terminated > at > org.python.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:821) > at > org.python.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:327) > at > org.python.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:320) > ... > > Maybe the SSL failure is a worry, but nothing else. > > Jeff > > > Jeff Allen > > > On 29/05/2017 19:17, fwi...@gm... > <mailto:fwi...@gm...> 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-1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar > <https://oss.sonatype.org/content/repositories/orgpython-1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar> > > standalone: > https://oss.sonatype.org/content/repositories/orgpython-1066/org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.jar > <https://oss.sonatype.org/content/repositories/orgpython-1066/org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.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 > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > <mailto:Jyt...@li...> > https://lists.sourceforge.net/lists/listinfo/jython-dev > <https://lists.sourceforge.net/lists/listinfo/jython-dev> > > > |
|
From: Jim B. <jim...@py...> - 2017-05-30 01:47:20
|
I also tested the installer on Ubuntu 16.04.2 LTS with Java 8 (1.8.0_131), and it works as expected (regrtest, yolk smoke test); I also tested the standalone jar. More below. Given Jeff's testing on Windows — very nice that Jython now works with Unicode in the username! — we have completed basic sanity checks and *we can finalize this RC2*. I haven't really tried to do much testing with the standalone jar in the past, in part because all the tests are stripped from it. However, it is possible to run most of the tests, excluding introspective type tests that try to look up Python files that are enclosed in the standalone jar (not going to work before we fix http://bugs.jython.org/issue2143). Also interestingly it is possible to do the following with the standalone jar: $ java -jar jython-standalone-2.7.1-rc2.jar -m ensurepip Collecting setuptools Collecting pip Installing collected packages: setuptools, pip Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython Failed to open /Users/jbaker/jythondev/test-standalone/bin/jython Successfully installed pip-9.0.1 setuptools-28.8.0 jimbaker:test-standalone jbaker$ java -jar jython-standalone-2.7.1-rc2.jar -m pip install pytz Collecting pytz Downloading pytz-2017.2-py2.py3-none-any.whl (484kB) 100% |████████████████████████████████| 491kB 556kB/s Installing collected packages: pytz Successfully installed pytz-2017.2 And then use the pytz package etc. Such packages are simply installed in Lib/site-packages, which will be created if missing. JYTHONPATH probably needs to be set properly for all this to work. Interesting detail that I hadn't connected before myself. On Mon, May 29, 2017 at 7:27 PM, Jim Baker <jim...@py...> wrote: > I tested the installation on OSX 10.12 (Sierra), including the smoke test > for pip/setuptools (yolk) and the regrtest, and it works as expected. > > As I mentioned in http://bugs.jython.org/issue2594, test_load_cert_chain > in test_ssl relies on signed jars in Bouncy Castle. Fortunately if those > jars are on the CLASSPATH, they will precede Jython's shaded/uber jar > variants. > > > > On Mon, May 29, 2017 at 6:25 PM, Jeff Allen <ja...@fa...> wrote: > >> This installed fine for me on Windows (actually for user 用户名), including >> pip & setuptools. >> >> I ran the regression test as ..\2.7.1-rc2\bin\jython -m test.regrtest -e >> and got 3 failures. >> >> 372 tests OK. >> 7 tests skipped: >> test_codecmaps_hk test_curses test_smtpnet test_socketserver >> test_subprocess test_urllib2net test_urllibnet >> 3 tests failed: >> test___all__ test_inspect test_ssl >> 3 fails unexpected: >> test___all__ test_inspect test_ssl >> >> test___all__ fails on a missing ServeletException see >> http://bugs.jython.org/issue2308 >> >> ..\2.7.1-rc2\bin\jython -m test.test_inspect >> ..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect >> pass when re-run in isolation. >> >> ..\2.7.1-rc2\bin\jython -m test.test_ssl >> fails as reported in http://bugs.jython.org/issue2594 >> >> Passing test with Netty shower: >> >> test_socket >> May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap >> setChannelOption >> WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id: >> 0x286e32d1]' >> May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap >> setChannelOption >> WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id: >> 0x666fcd99]' >> May 29, 2017 8:28:40 PM org.python.netty.util.concurrent.DefaultPromise >> safeExecute >> SEVERE: Failed to submit a listener notification task. Event loop shut >> down? >> java.util.concurrent.RejectedExecutionException: event executor >> terminated >> at org.python.netty.util.concurrent.SingleThreadEventExecutor.r >> eject(SingleThreadEventExecutor.java:821) >> at org.python.netty.util.concurrent.SingleThreadEventExecutor.o >> fferTask(SingleThreadEventExecutor.java:327) >> at org.python.netty.util.concurrent.SingleThreadEventExecutor.a >> ddTask(SingleThreadEventExecutor.java:320) >> ... >> >> Maybe the SSL failure is a worry, but nothing else. >> >> Jeff >> >> >> Jeff Allen >> >> >> On 29/05/2017 19:17, fwi...@gm... 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-1065 >>> /org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar >>> >>> standalone: https://oss.sonatype.org/content/repositories/orgpython-1066 >>> /org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.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 >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >>> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jython-dev mailing list >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> > > |
|
From: Jim B. <jim...@py...> - 2017-05-29 23:27:32
|
I tested the installation on OSX 10.12 (Sierra), including the smoke test for pip/setuptools (yolk) and the regrtest, and it works as expected. As I mentioned in http://bugs.jython.org/issue2594, test_load_cert_chain in test_ssl relies on signed jars in Bouncy Castle. Fortunately if those jars are on the CLASSPATH, they will precede Jython's shaded/uber jar variants. On Mon, May 29, 2017 at 6:25 PM, Jeff Allen <ja...@fa...> wrote: > This installed fine for me on Windows (actually for user 用户名), including > pip & setuptools. > > I ran the regression test as ..\2.7.1-rc2\bin\jython -m test.regrtest -e > and got 3 failures. > > 372 tests OK. > 7 tests skipped: > test_codecmaps_hk test_curses test_smtpnet test_socketserver > test_subprocess test_urllib2net test_urllibnet > 3 tests failed: > test___all__ test_inspect test_ssl > 3 fails unexpected: > test___all__ test_inspect test_ssl > > test___all__ fails on a missing ServeletException see > http://bugs.jython.org/issue2308 > > ..\2.7.1-rc2\bin\jython -m test.test_inspect > ..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect > pass when re-run in isolation. > > ..\2.7.1-rc2\bin\jython -m test.test_ssl > fails as reported in http://bugs.jython.org/issue2594 > > Passing test with Netty shower: > > test_socket > May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap > setChannelOption > WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id: > 0x286e32d1]' > May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap > setChannelOption > WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id: > 0x666fcd99]' > May 29, 2017 8:28:40 PM org.python.netty.util.concurrent.DefaultPromise > safeExecute > SEVERE: Failed to submit a listener notification task. Event loop shut > down? > java.util.concurrent.RejectedExecutionException: event executor terminated > at org.python.netty.util.concurrent.SingleThreadEventExecutor.r > eject(SingleThreadEventExecutor.java:821) > at org.python.netty.util.concurrent.SingleThreadEventExecutor.o > fferTask(SingleThreadEventExecutor.java:327) > at org.python.netty.util.concurrent.SingleThreadEventExecutor.a > ddTask(SingleThreadEventExecutor.java:320) > ... > > Maybe the SSL failure is a worry, but nothing else. > > Jeff > > > Jeff Allen > > > On 29/05/2017 19:17, fwi...@gm... 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- >> 1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar >> >> standalone: https://oss.sonatype.org/content/repositories/orgpython- >> 1066/org/python/jython-standalone/2.7.1-rc2/jython- >> standalone-2.7.1-rc2.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 >> Jyt...@li... >> https://lists.sourceforge.net/lists/listinfo/jython-dev >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |
|
From: Jeff A. <ja...@fa...> - 2017-05-29 22:26:00
|
This installed fine for me on Windows (actually for user 用户名), including
pip & setuptools.
I ran the regression test as ..\2.7.1-rc2\bin\jython -m test.regrtest -e
and got 3 failures.
372 tests OK.
7 tests skipped:
test_codecmaps_hk test_curses test_smtpnet test_socketserver
test_subprocess test_urllib2net test_urllibnet
3 tests failed:
test___all__ test_inspect test_ssl
3 fails unexpected:
test___all__ test_inspect test_ssl
test___all__ fails on a missing ServeletException see
http://bugs.jython.org/issue2308
..\2.7.1-rc2\bin\jython -m test.test_inspect
..\2.7.1-rc2\bin\jython -m test.regrtest test_inspect
pass when re-run in isolation.
..\2.7.1-rc2\bin\jython -m test.test_ssl
fails as reported in http://bugs.jython.org/issue2594
Passing test with Netty shower:
test_socket
May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap
setChannelOption
WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id:
0x286e32d1]'
May 29, 2017 8:28:36 PM org.python.netty.bootstrap.AbstractBootstrap
setChannelOption
WARNING: Unknown channel option 'SO_KEEPALIVE' for channel '[id:
0x666fcd99]'
May 29, 2017 8:28:40 PM org.python.netty.util.concurrent.DefaultPromise
safeExecute
SEVERE: Failed to submit a listener notification task. Event loop shut down?
java.util.concurrent.RejectedExecutionException: event executor terminated
at
org.python.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:821)
at
org.python.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:327)
at
org.python.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:320)
...
Maybe the SSL failure is a worry, but nothing else.
Jeff
Jeff Allen
On 29/05/2017 19:17, fwi...@gm... 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-1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar
>
> standalone: https://oss.sonatype.org/content/repositories/orgpython-1066/org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.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
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
|
|
From: Jeff A. <ja...@fa...> - 2017-05-29 21:53:33
|
On 29/05/2017 18:30, fwi...@gm... wrote: > On Mon, May 29, 2017 at 3:07 AM, Jeff Allen <ja...@fa...> wrote: >> * Although I believe I could commit directly to >> https://github.com/jython/jython3, or a branch in there, do we agree >> a better practice is to fork, branch and create a PR for a "feature" >> (groups of related commits)? Even if I then accept my own PR, it >> seems to give us a better audit trail, integration test, squash >> point, etc.. A separate thread/discussion is due about workflow, >> naming, etc.. > That sounds good to me. I haven't studied CPython's workflow for > github, but in general I think we should try to do what they do. > Since I wrote, I've been looking at CPython's workflow now based on GitHub. For the contributor there are straightforward instructions here: https://docs.python.org/devguide/ that include fork, branch and PR as I expected. Interestingly we're asked to raise an issue on tracker at bugs.python.org, not at GitHub, so it's not just a repository of pre-existing issues. Here's an example of that working: https://github.com/python/cpython/pull/1853 There are some helpful bots, including an integration with bugs.python.org that checks for a contributor agreement. I think we could not copy this unless we bring our tracker up to the same state as the CPython one. I like the bot that @mentions core developers as reviewers, based on who worked on the files you touched. Behind the scenes it is more complicated. A description of the branching and tagging is here: https://docs.python.org/devguide/devcycle.html#branches, including some rules about what alpha, beta, RC should mean in terms of acceptable commits. This all looks very sensible to me and I imagine it is essentially the same as it was for Mercurial. More examples ... Here Serhiy Storchaka makes a PR for a change consisting of (as I write) a couple of commits. (https://github.com/python/cpython/pull/1851) Even though he is a core developer, and the master branch is the active development branch, the work originates on a feature branch in his own forked repo. This gives us a chance to comment and him a chance to see it tested by Travis etc.. If I've understood the rules, Serhiy would be able to merge this into the master branch on his own approval. In another example, the feature branch is on the central repository (https://github.com/python/cpython/pull/1855). I think Alex has got the process wrong, and it should have been on his own fork, but maybe there's a good reason, and I think there's no permanent harm. Here's a more complicated example in which a change from a contributor is committed on master (by Serhiy) and then cherry-picked by Mariatta onto the 2.7, 3.5 and 3.6 branches. (https://github.com/python/cpython/pull/1019) This picking happens via branches on her own repository. The merge doesn't go smoothly on 2.7, but the problem is resolved with help from Serhiy. (https://github.com/python/cpython/pull/1289) Thus in spite of the difficulty, nothing hits the 2.7 branch until it is correct. Mariatta's branches are not visible any more since she is able to delete them after the merge. Jeff |
|
From: Jeff A. <ja...@fa...> - 2017-05-29 20:04:58
|
The difficulty of such merging can be tested in a local repository, I think. I don't have enough git knowledge to predict. Frank has answered, as I hoped, in terms that will help all budding contributors. Jeff Allen On 29/05/2017 18:35, Stefan Richthofer wrote: > (sorry, don't know the answers to your actual questions, actually I have somewhat the same questions) > >> Maybe my perception is coloured by the work I did last, which was very specific to Python 2, and doesn't belong in 3 > I guess my perception is coloured by work on metaclass issues, diamond inheritance issues w.r.t. slots etc. > Also unifying PyDict and PyStringMap, adding Py.newJ contructors, and plenty of other examples that I think do apply to Jython 3 as well. Porting them will be significant work, so exploring a somewhat automatic approach would be vital. It would be already a huge win if it could do 40-50% of the work. The remaining work will already be more than enough and involve plenty of cherry picking... > > > >> Gesendet: Montag, 29. Mai 2017 um 17:26 Uhr >> Von: "Jeff Allen" <ja...@fa...> >> An: "Stefan Richthofer" <Ste...@gm...>, "Jython Developers" <jyt...@li...> >> Betreff: Re: [Jython-dev] Jython 3: greenhorn questions from an old hand >> >> Maybe my perception is coloured by the work I did last, which was very >> specific to Python 2, and doesn't belong in 3, but I'd dismissed any >> mechanical merge as impossible or inadvisable. I think each change we >> made to 2 will need cherry-picking on its merits, but you're right about >> doing it systematically. This may actually be what I spend time doing. >> >> Given the pervasive nature of the (close to 700) changes on the Jython 3 >> fork, it seems likely there would be constant conflict. I expect to >> spend a lot of time with Kdiff3. >> >> Quite understand about your GSoC commitment: don't worry, we won't go >> far without you. :/ >> >> Would appreciate answers to my newbie questions. >> >> Jeff >> >> Jeff Allen >> >> On 29/05/2017 15:31, Stefan Richthofer wrote: >>> I really recommend that we (at least try to) merge 2.7.1 work into Jython 3 as far as and wherever possible. >>> That means, really go back to the spot where 3 was forked from 2.7 and look at every single commit and merge it. >>> I suppose this can be done in a semi-automated manner. Maybe it's not possible entirely with github GUI, but >>> maybe we can save the changesets somehow. Git certainly has a way to use a changeset file as input for its >>> merging algorithm. Ideally we would have a script that applies all changes that are automatically mergable. >>> Every changeset that cannot be merged automatically should get a look (from its author ideally). >>> Either it can be adjusted with reasonable effort, or it is maybe not applicable to Jython 3 for fundamental reasons. >>> >>> We should do this before Jython 3 and 2 diverge even more. Chances that automatic approach is vastly applicable will >>> decrease more and more. I really doubt I can motivate myself much to work on a Jython 3 codebase that is full of >>> issues we already solved. I'd rather much prefer to fix things that might break due to the merge process. >>> >>> Unfortunately I cannot help much on this process right now, because GSoC is about to launch. >>> Will be in for Jython 3 later this year again. >>> >>> Best >>> >>> -Stefan >>> >>> >>> >>>> Gesendet: Montag, 29. Mai 2017 um 12:07 Uhr >>>> Von: "Jeff Allen" <ja...@fa...> >>>> An: "Jython Developers" <jyt...@li...> >>>> Betreff: [Jython-dev] Jython 3: greenhorn questions from an old hand >>>> >>>> With 2.7.1 seemingly on its release journey, I have a bit of time to >>>> hack on Jython 3. A lot has been done to Jython 3 since it forked from >>>> 2, so I have some really newbie questions: >>>> >>>> * Is https://github.com/jython/jython3 the official reference >>>> repository? (Is https://hg.python.org/sandbox/jython3 dead?) >>>> * Are we still building with Ant? (It didn't for me on Windows, and I >>>> thought I'd fix that first.) BTW, this is a question about now, not >>>> what we'd like to do in future. >>>> * Versions: Java 8, and Python 3.5? >>>> * Although I believe I could commit directly to >>>> https://github.com/jython/jython3, or a branch in there, do we agree >>>> a better practice is to fork, branch and create a PR for a "feature" >>>> (groups of related commits)? Even if I then accept my own PR, it >>>> seems to give us a better audit trail, integration test, squash >>>> point, etc.. A separate thread/discussion is due about workflow, >>>> naming, etc.. >>>> * Do we agree that our aim is to run the CPython regression tests with >>>> as few skips, exclusions and replacement tests as possible? >>>> * Does anyone have code stored up that I risk duplicating? (E.g. >>>> Somewhere, Darjus mentioned ANTLR4 migration.) Otherwise I'll just >>>> start with things I know about (bytes and strings, buffer interface, >>>> io, import perhaps), driven by getting Py3k tests to pass honestly. >>>> >>>> I will averaging much fewer than 3 commits a day. ;) >>>> >>>> -- >>>> >>>> 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 >>>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jython-dev mailing list >>> Jyt...@li... >>> https://lists.sourceforge.net/lists/listinfo/jython-dev >>> >> |
|
From: <fwi...@gm...> - 2017-05-29 18:28:49
|
On Mon, May 29, 2017 at 11:22 AM, Stefan Richthofer <Ste...@gm...> wrote: > Along with language and runtime compatibility with CPython > 2.7, Jython 2.7.1 provides substantial support of the Python Agreed, I went ahead and made that change now so I don't forget :) |
|
From: Stefan R. <Ste...@gm...> - 2017-05-29 18:22:57
|
Frank, right after your recent commits I saw the text snippet in the readme.txt: Along with language and runtime compatibility with CPython 2.7.1, Jython 2.7 provides substantial support of the Python I think the explicit reference to CPython 2.7.1 is misleading. It implies that Jython micro version aligns with CPython micro version and IIRC we recently agreed that this cannot be the case. Maybe it should better read: Along with language and runtime compatibility with CPython 2.7, Jython 2.7.1 provides substantial support of the Python I suppose such a change needn't interrupt the pending rc2 release. Readme adjustments should be fine between RC2 and final. -Stefan |
|
From: <fwi...@gm...> - 2017-05-29 18:18:44
|
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-1065/org/python/jython-installer/2.7.1-rc2/jython-installer-2.7.1-rc2.jar standalone: https://oss.sonatype.org/content/repositories/orgpython-1066/org/python/jython-standalone/2.7.1-rc2/jython-standalone-2.7.1-rc2.jar The parent directories of each of the above have the checksums, source jars, javadocs, etc. -Frank |
|
From: Stefan R. <Ste...@gm...> - 2017-05-29 17:35:15
|
(sorry, don't know the answers to your actual questions, actually I have somewhat the same questions) > Maybe my perception is coloured by the work I did last, which was very specific to Python 2, and doesn't belong in 3 I guess my perception is coloured by work on metaclass issues, diamond inheritance issues w.r.t. slots etc. Also unifying PyDict and PyStringMap, adding Py.newJ contructors, and plenty of other examples that I think do apply to Jython 3 as well. Porting them will be significant work, so exploring a somewhat automatic approach would be vital. It would be already a huge win if it could do 40-50% of the work. The remaining work will already be more than enough and involve plenty of cherry picking... > Gesendet: Montag, 29. Mai 2017 um 17:26 Uhr > Von: "Jeff Allen" <ja...@fa...> > An: "Stefan Richthofer" <Ste...@gm...>, "Jython Developers" <jyt...@li...> > Betreff: Re: [Jython-dev] Jython 3: greenhorn questions from an old hand > > Maybe my perception is coloured by the work I did last, which was very > specific to Python 2, and doesn't belong in 3, but I'd dismissed any > mechanical merge as impossible or inadvisable. I think each change we > made to 2 will need cherry-picking on its merits, but you're right about > doing it systematically. This may actually be what I spend time doing. > > Given the pervasive nature of the (close to 700) changes on the Jython 3 > fork, it seems likely there would be constant conflict. I expect to > spend a lot of time with Kdiff3. > > Quite understand about your GSoC commitment: don't worry, we won't go > far without you. :/ > > Would appreciate answers to my newbie questions. > > Jeff > > Jeff Allen > > On 29/05/2017 15:31, Stefan Richthofer wrote: > > I really recommend that we (at least try to) merge 2.7.1 work into Jython 3 as far as and wherever possible. > > That means, really go back to the spot where 3 was forked from 2.7 and look at every single commit and merge it. > > I suppose this can be done in a semi-automated manner. Maybe it's not possible entirely with github GUI, but > > maybe we can save the changesets somehow. Git certainly has a way to use a changeset file as input for its > > merging algorithm. Ideally we would have a script that applies all changes that are automatically mergable. > > Every changeset that cannot be merged automatically should get a look (from its author ideally). > > Either it can be adjusted with reasonable effort, or it is maybe not applicable to Jython 3 for fundamental reasons. > > > > We should do this before Jython 3 and 2 diverge even more. Chances that automatic approach is vastly applicable will > > decrease more and more. I really doubt I can motivate myself much to work on a Jython 3 codebase that is full of > > issues we already solved. I'd rather much prefer to fix things that might break due to the merge process. > > > > Unfortunately I cannot help much on this process right now, because GSoC is about to launch. > > Will be in for Jython 3 later this year again. > > > > Best > > > > -Stefan > > > > > > > >> Gesendet: Montag, 29. Mai 2017 um 12:07 Uhr > >> Von: "Jeff Allen" <ja...@fa...> > >> An: "Jython Developers" <jyt...@li...> > >> Betreff: [Jython-dev] Jython 3: greenhorn questions from an old hand > >> > >> With 2.7.1 seemingly on its release journey, I have a bit of time to > >> hack on Jython 3. A lot has been done to Jython 3 since it forked from > >> 2, so I have some really newbie questions: > >> > >> * Is https://github.com/jython/jython3 the official reference > >> repository? (Is https://hg.python.org/sandbox/jython3 dead?) > >> * Are we still building with Ant? (It didn't for me on Windows, and I > >> thought I'd fix that first.) BTW, this is a question about now, not > >> what we'd like to do in future. > >> * Versions: Java 8, and Python 3.5? > >> * Although I believe I could commit directly to > >> https://github.com/jython/jython3, or a branch in there, do we agree > >> a better practice is to fork, branch and create a PR for a "feature" > >> (groups of related commits)? Even if I then accept my own PR, it > >> seems to give us a better audit trail, integration test, squash > >> point, etc.. A separate thread/discussion is due about workflow, > >> naming, etc.. > >> * Do we agree that our aim is to run the CPython regression tests with > >> as few skips, exclusions and replacement tests as possible? > >> * Does anyone have code stored up that I risk duplicating? (E.g. > >> Somewhere, Darjus mentioned ANTLR4 migration.) Otherwise I'll just > >> start with things I know about (bytes and strings, buffer interface, > >> io, import perhaps), driven by getting Py3k tests to pass honestly. > >> > >> I will averaging much fewer than 3 commits a day. ;) > >> > >> -- > >> > >> 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 > >> > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Jython-dev mailing list > > Jyt...@li... > > https://lists.sourceforge.net/lists/listinfo/jython-dev > > > > |
|
From: <fwi...@gm...> - 2017-05-29 17:31:37
|
On Mon, May 29, 2017 at 3:07 AM, Jeff Allen <ja...@fa...> wrote: > With 2.7.1 seemingly on its release journey, I have a bit of time to hack on > Jython 3. A lot has been done to Jython 3 since it forked from 2, so I have > some really newbie questions: > > * Is https://github.com/jython/jython3 the official reference > repository? (Is https://hg.python.org/sandbox/jython3 dead?) Yes, the github repo is the right one to look at. In the beginning of Isaiah Peng's amazing contributions, I reviewed his commits carefully. Things where improving so much so fast that I just let them go after a while. I'm sure there will be some places where we will want to adjust things. I know there are some commits in there for convenience that I wouldn't want pulled over as is (for example src/com/ziclix/ and src/org/python/indexer/ where removed - I'd prefer that we move them to their own directories like we do with installer/. In the case of ziclix, I'd like to eventually replace those with https://bitbucket.org/clach04/jyjdbc/ but it isn't a full replacement yet (I have permission from the author, my fault that it isn't in yet). > * Are we still building with Ant? (It didn't for me on Windows, and I > thought I'd fix that first.) BTW, this is a question about now, not > what we'd like to do in future. Yes, we are still on ant for Jython3 > * Versions: Java 8, and Python 3.5? I'm for aggressively using the latest Java for Jython3, pretty much whatever is the latest when we actually release. Given how big of a task this will be, I'm sure that will be at least Java 9 in the end :). I'm pretty sure the current Jython3 is focused on 3.5, but I'd be fine with pointing to 3.6. Once we are serious about Jython3, we probably should pick a version and see it through, as it definitely takes more work to switch Python versions vs Java versions. > * Although I believe I could commit directly to > https://github.com/jython/jython3, or a branch in there, do we agree > a better practice is to fork, branch and create a PR for a "feature" > (groups of related commits)? Even if I then accept my own PR, it > seems to give us a better audit trail, integration test, squash > point, etc.. A separate thread/discussion is due about workflow, > naming, etc.. That sounds good to me. I haven't studied CPython's workflow for github, but in general I think we should try to do what they do. > * Do we agree that our aim is to run the CPython regression tests with > as few skips, exclusions and replacement tests as possible? Yes, and one of my dream projects is to get as many of our changes into CPython's standard lib as possible, with an ultimate goal of removing our own Lib/ directory altogether. > * Does anyone have code stored up that I risk duplicating? (E.g. > Somewhere, Darjus mentioned ANTLR4 migration.) Otherwise I'll just > start with things I know about (bytes and strings, buffer interface, > io, import perhaps), driven by getting Py3k tests to pass honestly. Not me :) > > I will averaging much fewer than 3 commits a day. ;) > > -- > > 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 |
101 messages has been excluded from this view by a project administrator.
