From tracker at bugs.pypy.org Fri Mar 1 12:02:30 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Fri, 01 Mar 2013 11:02:30 +0000 Subject: [pypy-issue] [issue1411] fix tparm In-Reply-To: <1362135750.74.0.117731175662.issue1411@bugs.pypy.org> Message-ID: <1362135750.74.0.117731175662.issue1411@bugs.pypy.org> New submission from YAMAMOTO Takashi : this patch fixes the number of args of tparm. cf. http://pubs.opengroup.org/onlinepubs/7908799/xcurses/tparm.html the bug doesn't cause actual problems on systems where tparm takes varargs. but there are systems where tparm takes fixed number of arguments as xcurses prototype does. eg. netbsd. ---------- files: tparm-narg.diff messages: 5392 nosy: pypy-issue, yamt priority: bug status: unread title: fix tparm ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 1 12:06:49 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Fri, 01 Mar 2013 11:06:49 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> New submission from YAMAMOTO Takashi : this patch makes dotviewer stop hardcoding the path of cpython. there are various places it might be. eg. /usr/pkg/bin/python, ~/bin/python, etc. so it's better to just rely on PATH. ---------- files: dotviewer-python-path.diff messages: 5393 nosy: pypy-issue, yamt priority: bug status: unread title: dotviewer python path ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 1 12:10:33 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Fri, 01 Mar 2013 11:10:33 +0000 Subject: [pypy-issue] [issue1409] netbsd support In-Reply-To: <1361857361.33.0.161819094579.issue1409@bugs.pypy.org> Message-ID: <1362136233.62.0.0621552573869.issue1409@bugs.pypy.org> YAMAMOTO Takashi added the comment: thanks for applying the patch! here's an additional patch. on netbsd, 3rd party software like libffi is commonly installed in /usr/pkg/lib. so it's more convenient if rpython specifies -Wl,-R for the path automatically. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 1 12:14:06 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Fri, 01 Mar 2013 11:14:06 +0000 Subject: [pypy-issue] [issue1413] dotviewer fixes In-Reply-To: <1362136446.53.0.430751955748.issue1413@bugs.pypy.org> Message-ID: <1362136446.53.0.430751955748.issue1413@bugs.pypy.org> New submission from YAMAMOTO Takashi : this patch fixes two problems. - fix a unicode vs str problem. - avoid importing pygame from graph client. ---------- files: dotviewer-fixes.diff messages: 5395 nosy: pypy-issue, yamt priority: bug status: unread title: dotviewer fixes ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 1 22:58:12 2013 From: tracker at bugs.pypy.org (bdk) Date: Fri, 01 Mar 2013 21:58:12 +0000 Subject: [pypy-issue] [issue1409] netbsd support In-Reply-To: <1361857361.33.0.161819094579.issue1409@bugs.pypy.org> Message-ID: <1362175092.04.0.51137677778.issue1409@bugs.pypy.org> bdk added the comment: applied. feel free to re-open if you have more patches. ---------- status: testing -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 2 04:16:04 2013 From: tracker at bugs.pypy.org (bdk) Date: Sat, 02 Mar 2013 03:16:04 +0000 Subject: [pypy-issue] [issue1411] fix tparm In-Reply-To: <1362135750.74.0.117731175662.issue1411@bugs.pypy.org> Message-ID: <1362194164.83.0.0732065264835.issue1411@bugs.pypy.org> bdk added the comment: applied in d99f561336c6, thanks. ---------- nosy: +bdk status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 2 16:31:47 2013 From: tracker at bugs.pypy.org (wagstaff) Date: Sat, 02 Mar 2013 15:31:47 +0000 Subject: [pypy-issue] [issue725] Bug in zipimporting in nested packages In-Reply-To: <1305720180.28.0.132370010701.issue725@bugs.pypy.org> Message-ID: <1362238307.06.0.944629184206.issue725@bugs.pypy.org> wagstaff added the comment: Just noting that this is still broken - I'm running on Windows Vista - and that as linq reports, this prevents pypy from working with virtualenv on Windows. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 3 19:03:58 2013 From: tracker at bugs.pypy.org (bdk) Date: Sun, 03 Mar 2013 18:03:58 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362333838.15.0.208050602306.issue1412@bugs.pypy.org> bdk added the comment: it seems this was done intentionally when running on pypy to find a cpython? meaning your change would break behavior in a virtualenv. ---------- nosy: +bdk status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 3 19:13:41 2013 From: tracker at bugs.pypy.org (bdk) Date: Sun, 03 Mar 2013 18:13:41 +0000 Subject: [pypy-issue] [issue1413] dotviewer fixes In-Reply-To: <1362136446.53.0.430751955748.issue1413@bugs.pypy.org> Message-ID: <1362334421.0.0.95837499881.issue1413@bugs.pypy.org> bdk added the comment: pygame import is now avoided, but can you include a test for the msgstruct change? ---------- nosy: +bdk status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 3 19:58:56 2013 From: tracker at bugs.pypy.org (bdk) Date: Sun, 03 Mar 2013 18:58:56 +0000 Subject: [pypy-issue] [issue913] Reduce-like *functions* for micronumpy missing, e.g. numpy.dot In-Reply-To: <1318946612.94.0.137292123198.issue913@bugs.pypy.org> Message-ID: <1362337136.81.0.178061707522.issue913@bugs.pypy.org> bdk added the comment: vdot added in 3778a9fd5fe9 ---------- nosy: +bdk status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 3 20:07:56 2013 From: tracker at bugs.pypy.org (bdk) Date: Sun, 03 Mar 2013 19:07:56 +0000 Subject: [pypy-issue] [issue1404] Sync datetime optimizations from default to py3k? In-Reply-To: <1361307530.86.0.35638186243.issue1404@bugs.pypy.org> Message-ID: <1362337676.16.0.699878792574.issue1404@bugs.pypy.org> bdk added the comment: some were optimizations that probably apply to the py3k datetime.py, others were changes to make datetime.py behave more like cpython 2.7 builtin datetime, which you probably don't want to port. ---------- status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 4 03:53:16 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Mon, 04 Mar 2013 02:53:16 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362365596.22.0.18428287172.issue1412@bugs.pypy.org> YAMAMOTO Takashi added the comment: you mean running dotviewer and pypy in a virtualenv? ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 4 04:14:02 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Mon, 04 Mar 2013 03:14:02 +0000 Subject: [pypy-issue] [issue1413] dotviewer fixes In-Reply-To: <1362136446.53.0.430751955748.issue1413@bugs.pypy.org> Message-ID: <1362366842.53.0.135445804797.issue1413@bugs.pypy.org> YAMAMOTO Takashi added the comment: i forgot how to reproduce the msgstruct problem, sorry. please feel free to close this issue. i'll re-create an issue when i remember how to reproduce. btw, ./pytest.py dotviewer now complains. here's a patch to fix it. (i'm now familiar with pytest. i don't know if it's a right way to invoke the test.) ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 4 04:35:07 2013 From: tracker at bugs.pypy.org (bdk) Date: Mon, 04 Mar 2013 03:35:07 +0000 Subject: [pypy-issue] [issue1413] dotviewer fixes In-Reply-To: <1362136446.53.0.430751955748.issue1413@bugs.pypy.org> Message-ID: <1362368107.61.0.21427166615.issue1413@bugs.pypy.org> bdk added the comment: applied in 6d5c4347b06e, thanks ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 4 04:41:10 2013 From: tracker at bugs.pypy.org (bdk) Date: Mon, 04 Mar 2013 03:41:10 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362368470.76.0.788510953086.issue1412@bugs.pypy.org> bdk added the comment: yes, the logic of spawn_local_handler seems to imply it should spawn a cpython. it goes to /usr/bin/python if sys.executable is a pypy. but if inside a pypy virtualenv, /usr/bin/env python is another pypy, so this change wouldn't spawn a cpython as intended. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 4 12:32:00 2013 From: tracker at bugs.pypy.org (bdk) Date: Mon, 04 Mar 2013 11:32:00 +0000 Subject: [pypy-issue] [issue1343] datetime.utcnow() slow In-Reply-To: <1354196314.23.0.545969896857.issue1343@bugs.pypy.org> Message-ID: <1362396720.03.0.18871939344.issue1343@bugs.pypy.org> bdk added the comment: applied some more optimizations in 91b8e2795113 and 043d831e8736. we are now more than twice as fast as cpython's datetime module here. marking resolved. ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 4 12:34:39 2013 From: tracker at bugs.pypy.org (Gustavo Carneiro) Date: Mon, 04 Mar 2013 11:34:39 +0000 Subject: [pypy-issue] [issue1343] datetime.utcnow() slow In-Reply-To: <1354196314.23.0.545969896857.issue1343@bugs.pypy.org> Message-ID: <1362396879.19.0.179248242948.issue1343@bugs.pypy.org> Gustavo Carneiro added the comment: Awesome! :-) ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 00:34:19 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Mon, 04 Mar 2013 23:34:19 +0000 Subject: [pypy-issue] [issue1325] pypy + sqlite3 problem on Mac OSX In-Reply-To: <1352907788.82.0.816519768908.issue1325@bugs.pypy.org> Message-ID: <1362440059.7.0.709295483175.issue1325@bugs.pypy.org> Brian Kearns added the comment: fixed in 3bf4d0b6f5e8 (__del__ added for connection so db is closed on gc. still need to explicitly close or trigger a gc, but that's a wontfix pypy implementation detail) ---------- nosy: +bdk status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 06:30:14 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Tue, 05 Mar 2013 05:30:14 +0000 Subject: [pypy-issue] [issue1404] Sync datetime optimizations from default to py3k? In-Reply-To: <1361307530.86.0.35638186243.issue1404@bugs.pypy.org> Message-ID: <1362461414.66.0.061489660834.issue1404@bugs.pypy.org> Brian Kearns added the comment: ported these ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 07:50:43 2013 From: tracker at bugs.pypy.org (Kyle) Date: Tue, 05 Mar 2013 06:50:43 +0000 Subject: [pypy-issue] [issue1414] min()/max() performance In-Reply-To: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> Message-ID: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> New submission from Kyle : Using pypy2.0-beta1 I have managed to get performance boost up to 20x (for integers) and up to 10x (for strings) of min()/max() functions when reimplemented them in pure python as follows: def min_(arg): seq = iter(arg) head = seq.next() return reduce(min, seq, head) # min called with two args # With exception handling for empty sequence: def min_(arg): seq = iter(arg) # throws TypeError for non-iterables try: head = seq.next() except StopIteration: raise ValueError('arg is an empty sequence') return reduce(min, seq, head) Could you please investigate performance on your side? I understand that min/max functions should also fallback to compare function for two (or small amount of) arguments, but given large sequences we can neglect this difference. ---------- messages: 5411 nosy: dbud, pypy-issue priority: performance bug release: 2.0 status: unread title: min()/max() performance ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 08:01:24 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Tue, 05 Mar 2013 07:01:24 +0000 Subject: [pypy-issue] [issue1414] min()/max() performance In-Reply-To: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> Message-ID: <1362466884.36.0.321498834275.issue1414@bugs.pypy.org> Brian Kearns added the comment: this has been fixed, try again with nightly. ---------- nosy: +bdk status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 08:08:18 2013 From: tracker at bugs.pypy.org (Roy Feldman) Date: Tue, 05 Mar 2013 07:08:18 +0000 Subject: [pypy-issue] [issue1415] Kermit tests failing - interpreter not functional In-Reply-To: <1362467298.33.0.818386260109.issue1415@bugs.pypy.org> Message-ID: <1362467298.33.0.818386260109.issue1415@bugs.pypy.org> New submission from Roy Feldman : The same four tests in Kermit (aka example-interpreter) are failing in both 2.0- beta-1 and a recent revision "6d5c4347b06e", dated March 4. Two of the tests cause hang, test_jit in test_jit.py and test_while in test_interpreter.py. When those tests are commented out, py.test returns failures for test_print and test_if in test_interpreter.py. Without if, print, and while, there is very little that can be done with the Kermit interpreter. ---------- messages: 5413 nosy: pypy-issue priority: bug release: 2.0 status: unread title: Kermit tests failing - interpreter not functional ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 08:09:02 2013 From: tracker at bugs.pypy.org (Roy Feldman) Date: Tue, 05 Mar 2013 07:09:02 +0000 Subject: [pypy-issue] [issue1415] Kermit tests failing - interpreter not functional In-Reply-To: <1362467342.94.0.193022128287.issue1415@bugs.pypy.org> Message-ID: <1362467342.94.0.193022128287.issue1415@bugs.pypy.org> New submission from Roy Feldman : The same four tests in Kermit (aka example-interpreter) are failing in both 2.0- beta-1 and a recent revision "6d5c4347b06e", dated March 4. Two of the tests hang, test_jit in test_jit.py and test_while in test_interpreter.py. When those tests are commented out, py.test returns failures for test_print and test_if in test_interpreter.py. Without if, print, and while, there is very little that can be done with the Kermit interpreter. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 08:51:53 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Tue, 05 Mar 2013 07:51:53 +0000 Subject: [pypy-issue] [issue1415] Kermit tests failing - interpreter not functional In-Reply-To: <1362467342.94.0.193022128287.issue1415@bugs.pypy.org> Message-ID: <1362469913.7.0.985741688144.issue1415@bugs.pypy.org> Amaury Forgeot d Arc added the comment: The interpreter is indeed broken. - for print, W_Root objects need a str() method; - in JUMP_IF_FALSE, some boolean value of the object should be used: W_IntObject() is always True! ---------- assignedto: -> fijal nosy: +amaury, fijal ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 09:22:23 2013 From: tracker at bugs.pypy.org (Kyle) Date: Tue, 05 Mar 2013 08:22:23 +0000 Subject: [pypy-issue] [issue1414] min()/max() performance In-Reply-To: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> Message-ID: <1362471743.49.0.209578969862.issue1414@bugs.pypy.org> Kyle added the comment: Hi again, I have tried nightly (pypy-c-jit-61992-6fe2c02099ef-win32) and still got boost: code: import time class measure: def __init__(self, description, size, runs): self.description = description self.size = size self.runs = runs def __enter__(self): self.start = time.time() def __exit__(self, *args): elapsed = time.time() - self.start print '%.2lf runs/sec, %s, size = %d, %d runs' % (self.runs / elapsed, self.description, self.size, self.runs) def min_(arg): seq = iter(arg) try: head = seq.next() except StopIteration: raise ValueError('arg is an empty sequence') return reduce(min, seq, head) N = 1000 N_max = 100000000 while N <= N_max: K = 5 * N_max / N r = range(N) with measure('built-in', N, K): for _ in range(K): min(r) with measure('with reduce', N, K): for _ in range(K): min_(r) print N *= 10 output: 372300.84 runs/sec, built-in, size = 1000, 500000 runs 692520.66 runs/sec, with reduce, size = 1000, 500000 runs 29994.00 runs/sec, built-in, size = 10000, 50000 runs 77279.74 runs/sec, with reduce, size = 10000, 50000 runs 4012.84 runs/sec, built-in, size = 100000, 5000 runs 7874.02 runs/sec, with reduce, size = 100000, 5000 runs 388.50 runs/sec, built-in, size = 1000000, 500 runs 791.14 runs/sec, with reduce, size = 1000000, 500 runs 30.79 runs/sec, built-in, size = 10000000, 50 runs 79.24 runs/sec, with reduce, size = 10000000, 50 runs 0.98 runs/sec, built-in, size = 100000000, 5 runs 7.90 runs/sec, with reduce, size = 100000000, 5 runs ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 09:59:34 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Tue, 05 Mar 2013 08:59:34 +0000 Subject: [pypy-issue] [issue1414] min()/max() performance In-Reply-To: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> Message-ID: <1362473974.55.0.985847242541.issue1414@bugs.pypy.org> Brian Kearns added the comment: Sure, but it's nothing like the factor you talked about. Also, the 'boost' is not always positive: 15338900.77 runs/sec, built-in, size = 10, 50000000 runs 7145017.92 runs/sec, with reduce, size = 10, 50000000 runs 2966616.18 runs/sec, built-in, size = 100, 5000000 runs 3396951.23 runs/sec, with reduce, size = 100, 5000000 runs 344860.12 runs/sec, built-in, size = 1000, 500000 runs 563466.53 runs/sec, with reduce, size = 1000, 500000 runs There may be a remaining optimization to make for min/max, but I'm not even sure it is justifiably a bug; we're currently 5-6x CPython for builtin min/max. I'd say this is an example of a specific optimization for PyPy useful when calling min/max on very long lists (which possibly, though maybe not, could be made obsolete with later optimizations in PyPy). ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 15:38:54 2013 From: tracker at bugs.pypy.org (Kyle) Date: Tue, 05 Mar 2013 14:38:54 +0000 Subject: [pypy-issue] [issue1414] min()/max() performance In-Reply-To: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> Message-ID: <1362494334.34.0.759106992877.issue1414@bugs.pypy.org> Kyle added the comment: Thank you for the decent support. Sure, it is not a bug by any means, I was just curious about performance and the category seemed the most suitable :) I see that runs per second value varies greatly on different machines and built- in is generally better on small lists, so I would not suggest making any changes to pypy. I would just stick to reduce(...) in my case for extremely large sequences. You may close the issue, and, thank you. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 5 23:34:39 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Tue, 05 Mar 2013 22:34:39 +0000 Subject: [pypy-issue] [issue1414] min()/max() performance In-Reply-To: <1362466243.67.0.0880642859898.issue1414@bugs.pypy.org> Message-ID: <1362522879.62.0.107348062781.issue1414@bugs.pypy.org> Brian Kearns added the comment: Good news-- I was able to improve builtin min/max performance across all sizes and also improve speed when key is specified (in b730d41cd8ab). Builtin performance is now as good as or better than reduce for size < 10000000. There is still some degradation of performance in builtin as size >= 10000000 that doesn't happen with reduce, which may very well represent a bug, so leaving open. Previous: $ ./pypy-c-0 m.py 14277995.64 runs/sec, built-in, size = 10, 50000000 runs 6267714.09 runs/sec, with reduce, size = 10, 50000000 runs 6510680.37 runs/sec, built-in w/ key, size = 10, 50000000 runs 2926269.90 runs/sec, built-in, size = 100, 5000000 runs 3374338.42 runs/sec, with reduce, size = 100, 5000000 runs 843932.29 runs/sec, built-in w/ key, size = 100, 5000000 runs 344833.76 runs/sec, built-in, size = 1000, 500000 runs 563179.64 runs/sec, with reduce, size = 1000, 500000 runs 92365.00 runs/sec, built-in w/ key, size = 1000, 500000 runs 35048.42 runs/sec, built-in, size = 10000, 50000 runs 60476.38 runs/sec, with reduce, size = 10000, 50000 runs 9438.79 runs/sec, built-in w/ key, size = 10000, 50000 runs 3500.86 runs/sec, built-in, size = 100000, 5000 runs 6267.29 runs/sec, with reduce, size = 100000, 5000 runs 934.73 runs/sec, built-in w/ key, size = 100000, 5000 runs 346.31 runs/sec, built-in, size = 1000000, 500 runs 662.96 runs/sec, with reduce, size = 1000000, 500 runs 89.81 runs/sec, built-in w/ key, size = 1000000, 500 runs 29.98 runs/sec, built-in, size = 10000000, 50 runs 67.68 runs/sec, with reduce, size = 10000000, 50 runs 6.99 runs/sec, built-in w/ key, size = 10000000, 50 runs 1.28 runs/sec, built-in, size = 100000000, 5 runs 6.80 runs/sec, with reduce, size = 100000000, 5 runs 0.21 runs/sec, built-in w/ key, size = 100000000, 5 runs Now: $ ./pypy-c-3 m.py 21519222.96 runs/sec, built-in, size = 10, 50000000 runs 7251169.03 runs/sec, with reduce, size = 10, 50000000 runs 12548421.16 runs/sec, built-in w/ key, size = 10, 50000000 runs 5091281.99 runs/sec, built-in, size = 100, 5000000 runs 3418216.98 runs/sec, with reduce, size = 100, 5000000 runs 2713657.19 runs/sec, built-in w/ key, size = 100, 5000000 runs 623827.29 runs/sec, built-in, size = 1000, 500000 runs 563213.97 runs/sec, with reduce, size = 1000, 500000 runs 330590.96 runs/sec, built-in w/ key, size = 1000, 500000 runs 62983.00 runs/sec, built-in, size = 10000, 50000 runs 60356.07 runs/sec, with reduce, size = 10000, 50000 runs 34038.98 runs/sec, built-in w/ key, size = 10000, 50000 runs 6398.50 runs/sec, built-in, size = 100000, 5000 runs 6204.26 runs/sec, with reduce, size = 100000, 5000 runs 3410.64 runs/sec, built-in w/ key, size = 100000, 5000 runs 620.88 runs/sec, built-in, size = 1000000, 500 runs 664.87 runs/sec, with reduce, size = 1000000, 500 runs 307.46 runs/sec, built-in w/ key, size = 1000000, 500 runs 47.92 runs/sec, built-in, size = 10000000, 50 runs 68.11 runs/sec, with reduce, size = 10000000, 50 runs 14.86 runs/sec, built-in w/ key, size = 10000000, 50 runs 1.46 runs/sec, built-in, size = 100000000, 5 runs 6.80 runs/sec, with reduce, size = 100000000, 5 runs 0.24 runs/sec, built-in w/ key, size = 100000000, 5 runs ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 7 12:19:06 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Thu, 07 Mar 2013 11:19:06 +0000 Subject: [pypy-issue] [issue1415] Kermit tests failing - interpreter not functional In-Reply-To: <1362467342.94.0.193022128287.issue1415@bugs.pypy.org> Message-ID: <1362655146.14.0.470220086865.issue1415@bugs.pypy.org> Armin Rigo added the comment: Just to know, what is Kermit? ---------- nosy: +arigo ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 7 12:31:31 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Thu, 07 Mar 2013 11:31:31 +0000 Subject: [pypy-issue] [issue1198] AssertionError: must come from an argument to the function, got <-88; esp> In-Reply-To: <1341147966.42.0.760059580074.issue1198@bugs.pypy.org> Message-ID: <1362655891.21.0.820938161374.issue1198@bugs.pypy.org> Armin Rigo added the comment: Thanks, fixed in db608eb643ed. ---------- nosy: +arigo status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 7 14:46:04 2013 From: tracker at bugs.pypy.org (Fijal) Date: Thu, 07 Mar 2013 13:46:04 +0000 Subject: [pypy-issue] [issue1415] Kermit tests failing - interpreter not functional In-Reply-To: <1362467342.94.0.193022128287.issue1415@bugs.pypy.org> Message-ID: <1362663964.51.0.538001395584.issue1415@bugs.pypy.org> Fijal added the comment: kermit is here - https://bitbucket.org/pypy/example-interpreter and tests are fixed. ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 8 11:02:50 2013 From: tracker at bugs.pypy.org (Fijal) Date: Fri, 08 Mar 2013 10:02:50 +0000 Subject: [pypy-issue] [issue1416] Fix ARM hard floats In-Reply-To: <1362736970.03.0.69077399834.issue1416@bugs.pypy.org> Message-ID: <1362736970.03.0.69077399834.issue1416@bugs.pypy.org> New submission from Fijal : Hard floats on ARM backend are broken. This essentially prevents PyPy from working on virtually any interesting ARM. We should fix it before 2.0 final ---------- messages: 5423 nosy: fijal, pypy-issue priority: critical status: unread title: Fix ARM hard floats ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 8 22:49:12 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Fri, 08 Mar 2013 21:49:12 +0000 Subject: [pypy-issue] [issue1377] [ARM] problem with trackgcroot.py In-Reply-To: <1358807765.7.0.796115431702.issue1377@bugs.pypy.org> Message-ID: <1362779352.37.0.414537647877.issue1377@bugs.pypy.org> Armin Rigo added the comment: asmgcc is not supported on ARM. But we need to say "--gcrootfinder=shadowstack" explicitly? If so, can someone fix it? ---------- nosy: +arigo status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 8 22:50:52 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Fri, 08 Mar 2013 21:50:52 +0000 Subject: [pypy-issue] [issue1376] [ARM] generates invalid CFLAGS In-Reply-To: <1358806611.04.0.332529809983.issue1376@bugs.pypy.org> Message-ID: <1362779452.35.0.768602348022.issue1376@bugs.pypy.org> Armin Rigo added the comment: Same as with issue1377: can someone fix and test this? It looks like the default flags are rather bogus on ARM. ---------- nosy: +arigo status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 8 23:03:51 2013 From: tracker at bugs.pypy.org (Jay Wren) Date: Fri, 08 Mar 2013 22:03:51 +0000 Subject: [pypy-issue] [issue1417] pipe operator does not work as overriden with pipe module In-Reply-To: <1362780231.87.0.165433541684.issue1417@bugs.pypy.org> Message-ID: <1362780231.87.0.165433541684.issue1417@bugs.pypy.org> New submission from Jay Wren : would be nice if I could pip install pipe and then evens = xrange(100) | pipe.select(lambda i: i%2==0) | pipe.as_list ---------- messages: 5426 nosy: jrwren, pypy-issue priority: wish status: unread title: pipe operator does not work as overriden with pipe module ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 8 23:12:16 2013 From: tracker at bugs.pypy.org (Alex Gaynor) Date: Fri, 08 Mar 2013 22:12:16 +0000 Subject: [pypy-issue] [issue1417] pipe operator does not work as overriden with pipe module In-Reply-To: <1362780231.87.0.165433541684.issue1417@bugs.pypy.org> Message-ID: <1362780736.57.0.467793094609.issue1417@bugs.pypy.org> Alex Gaynor added the comment: Does this not work now? How does it fail? ---------- nosy: +agaynor status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 10 12:37:18 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Sun, 10 Mar 2013 11:37:18 +0000 Subject: [pypy-issue] [issue1417] pipe operator does not work as overriden with pipe module In-Reply-To: <1362780231.87.0.165433541684.issue1417@bugs.pypy.org> Message-ID: <1362915438.28.0.556103022348.issue1417@bugs.pypy.org> Armin Rigo added the comment: Works for me (pypy 2.0-beta-1). ---------- nosy: +arigo status: chatting -> invalid ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 10 12:43:22 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Sun, 10 Mar 2013 11:43:22 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362915802.3.0.785499865054.issue1412@bugs.pypy.org> Armin Rigo added the comment: Improved the situation with a37006b7fffa. Please re-open this if it's not enough. ---------- nosy: +arigo status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 03:51:08 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Mon, 11 Mar 2013 02:51:08 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362970268.41.0.728184959464.issue1412@bugs.pypy.org> YAMAMOTO Takashi added the comment: on NetBSD, the common path of cpython is /usr/pkg/bin/python. ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 05:11:25 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Mon, 11 Mar 2013 04:11:25 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362975085.46.0.311675535556.issue1412@bugs.pypy.org> Brian Kearns added the comment: further improved the situation/made the fix more universal in 05243549ef64 (now uses 'env -i which python', which should be a more proper solution) ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 08:12:25 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Mon, 11 Mar 2013 07:12:25 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362985945.17.0.434866926655.issue1412@bugs.pypy.org> YAMAMOTO Takashi added the comment: in which environment 'env -i which python' works? it didn't work for me on NetBSD, OSX, RHEL6. ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 09:06:17 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Mon, 11 Mar 2013 08:06:17 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362985945.17.0.434866926655.issue1412@bugs.pypy.org> Message-ID: Brian Kearns added the comment: right, seems latest ubuntu stable is ahead of the curve here. how about env -i bash -l -c "which python" on those? ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 09:50:20 2013 From: tracker at bugs.pypy.org (Fijal) Date: Mon, 11 Mar 2013 08:50:20 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362991820.37.0.514582306923.issue1412@bugs.pypy.org> Fijal added the comment: env -i will not respect your PATH (which is bad). I don't think there is a good way to do it. ---------- nosy: +fijal ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 10:33:34 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Mon, 11 Mar 2013 09:33:34 +0000 Subject: [pypy-issue] [issue1418] Wrong immutable_unique_id() for complex objects In-Reply-To: <1362994414.79.0.0685754343578.issue1418@bugs.pypy.org> Message-ID: <1362994414.79.0.0685754343578.issue1418@bugs.pypy.org> New submission from Amaury Forgeot d Arc : First reported in https://bitbucket.org/pypy/compatibility/issue/2/pyyaml-310-test-failure-with-complex Two distinct complex numbers can have the same id(): >>>> l = [-0.5j, 0.6-0.5j] >>>> map(id, l) (-36965545741457031161L, -36965545741457031161L) This breaks memoization in the Yaml serializer, but also pickle! >>>> pickle.loads(pickle.dumps(l)) [-0.5j, -0.5j] ---------- messages: 5435 nosy: amaury, pypy-issue priority: critical status: unread title: Wrong immutable_unique_id() for complex objects ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 10:51:49 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Mon, 11 Mar 2013 09:51:49 +0000 Subject: [pypy-issue] [issue1418] Wrong immutable_unique_id() for complex objects In-Reply-To: <1362994414.79.0.0685754343578.issue1418@bugs.pypy.org> Message-ID: <1362995509.43.0.660375433978.issue1418@bugs.pypy.org> Amaury Forgeot d Arc added the comment: Fixed by bdk in 18d3311a2498. ---------- status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 11:09:36 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Mon, 11 Mar 2013 10:09:36 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1362996576.72.0.885645485314.issue1412@bugs.pypy.org> Brian Kearns added the comment: ok. another attempt in 889d20441589. "should" work for most reasonable systems. if it doesn't work, chances are we aren't in a virtualenv anyways, and we fall back to current path. ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 14:33:37 2013 From: tracker at bugs.pypy.org (Jay Wren) Date: Mon, 11 Mar 2013 13:33:37 +0000 Subject: [pypy-issue] [issue1417] pipe operator does not work as overriden with pipe module In-Reply-To: <1362780231.87.0.165433541684.issue1417@bugs.pypy.org> Message-ID: <1363008817.31.0.443778503772.issue1417@bugs.pypy.org> Jay Wren added the comment: Closing this. My bad. I got an error which I assumed was pypy. I had just changed to trying pypy. There must have been some other error. The pipe module overrides the pipe operator as expected. Python 2.7.3 (7e4f0faa3d51, Nov 21 2012, 15:59:46) [PyPy 2.0.0-beta1 with GCC 4.2.1] on darwin Type "help", "copyright", "credits" or "license" for more information. And now for something completely different: ``happy PyPy's year 2010!'' >>>> import pipe >>>> range(0,100) | pipe.select(lambda i: i%2==0) at 0x000000010d5ce8e0> >>>> range(0,100) | pipe.select(lambda i: i%2==0) | pipe.as_list [True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False, True, False] >>>> range(0,100) | pipe.where(lambda i: i%2==0) | pipe.as_list [0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96, 98] Please, accept my apologies. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 18:55:38 2013 From: tracker at bugs.pypy.org (Stefan Behnel) Date: Mon, 11 Mar 2013 17:55:38 +0000 Subject: [pypy-issue] [issue1106] [cpyext] reassignments to tp_dict items don't have an effect In-Reply-To: <1333351389.24.0.00182077627071.issue1106@bugs.pypy.org> Message-ID: <1363024538.0.0.807015009691.issue1106@bugs.pypy.org> Stefan Behnel added the comment: Apparently, executing this after class creation provides a work-around: """ for name in Spam.__dict__: hasattr(Spam, name) """ ---------- status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 19:08:22 2013 From: tracker at bugs.pypy.org (Stefan Behnel) Date: Mon, 11 Mar 2013 18:08:22 +0000 Subject: [pypy-issue] [issue1106] [cpyext] reassignments to tp_dict items don't have an effect In-Reply-To: <1333351389.24.0.00182077627071.issue1106@bugs.pypy.org> Message-ID: <1363025302.27.0.275217404013.issue1106@bugs.pypy.org> Stefan Behnel added the comment: ... but not reliably, it seems. Meaning, it works *sometimes*, but not always. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 11 22:34:48 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Mon, 11 Mar 2013 21:34:48 +0000 Subject: [pypy-issue] [issue1106] [cpyext] reassignments to tp_dict items don't have an effect In-Reply-To: <1333351389.24.0.00182077627071.issue1106@bugs.pypy.org> Message-ID: <1363037688.66.0.392049718061.issue1106@bugs.pypy.org> Amaury Forgeot d Arc added the comment: The cause was in the type cache; PyType_Modified() used to be a no-op, which is wrong for extension types. Fixed with 889d20441589. ---------- nosy: +amaury status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 12 01:00:39 2013 From: tracker at bugs.pypy.org (YAMAMOTO Takashi) Date: Tue, 12 Mar 2013 00:00:39 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1363046439.15.0.551036527622.issue1412@bugs.pypy.org> YAMAMOTO Takashi added the comment: unfortunately it doesn't work on NetBSD because /bin/sh doesn't have -l option. i can't think of a portable way to achieve the goal. for BSD derivative systems whereis(1) is probably a right utility to use but linux distributions seem to have something incompatible with the same name. IMO, simply listing likely candidates (/usr/bin/python, /usr/local/bin/python, /usr/pkg/bin/python, ...) is a reasonable compromise. ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 12 01:18:30 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Tue, 12 Mar 2013 00:18:30 +0000 Subject: [pypy-issue] [issue1412] dotviewer python path In-Reply-To: <1362136009.66.0.091655820449.issue1412@bugs.pypy.org> Message-ID: <1363047510.26.0.0291140202916.issue1412@bugs.pypy.org> Brian Kearns added the comment: what shell is $SHELL on netbsd by default for users? does virtualenv even work with such limited shells? i doubt it. in which case the change as is will work fine. relying on current PATH on systems with such limited shells (which is what will happen when env -i $SHELL -l fails) seems fine -- chances that the user is running inside a virtualenv are basically zero. the failure case you presented is resolved. ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 12 02:01:01 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Tue, 12 Mar 2013 01:01:01 +0000 Subject: [pypy-issue] [issue1418] Wrong immutable_unique_id() for complex objects In-Reply-To: <1362994414.79.0.0685754343578.issue1418@bugs.pypy.org> Message-ID: <1363050061.98.0.644546536214.issue1418@bugs.pypy.org> Armin Rigo added the comment: Phew. Sorry and thanks for the fix. ---------- nosy: +arigo status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 12 12:09:56 2013 From: tracker at bugs.pypy.org (Antonio Cuni) Date: Tue, 12 Mar 2013 11:09:56 +0000 Subject: [pypy-issue] [issue1419] numpypy crash when using bool indices and a different dtype In-Reply-To: <1363086596.6.0.657951887248.issue1419@bugs.pypy.org> Message-ID: <1363086596.6.0.657951887248.issue1419@bugs.pypy.org> New submission from Antonio Cuni : The following code makes numpypy crasing: import numpypy x = numpypy.array([1,2,3,4,5], 'd') x[x<3] = 0 print x [...] File "./pypy/bin/../../pypy/module/micronumpy/interp_numarray.py", line 174, in descr_setitem convert_to_array(space, w_value)) File "./pypy/bin/../../pypy/module/micronumpy/interp_numarray.py", line 92, in setitem_filter loop.setitem_filter(self, idx, val) File "./pypy/bin/../../pypy/module/micronumpy/loop.py", line 339, in setitem_filter arr_iter.setitem(value_iter.getitem()) File "./pypy/bin/../../pypy/module/micronumpy/iter.py", line 170, in setitem self.dtype.setitem(self.array, self.offset, elem) File "./pypy/bin/../../pypy/module/micronumpy/interp_dtype.py", line 85, in setitem self.itemtype.store(arr, i, 0, box) File "./pypy/bin/../../pypy/module/micronumpy/types.py", line 186, in store self._write(arr.storage, i, offset, self.unbox(box)) File "./pypy/bin/../../pypy/module/micronumpy/types.py", line 149, in unbox assert isinstance(box, self.BoxType) AssertionError if you use 0.0 instead of 0, it works correctly ---------- messages: 5445 nosy: pypy-issue priority: bug status: unread title: numpypy crash when using bool indices and a different dtype ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 13 12:54:10 2013 From: tracker at bugs.pypy.org (Ian Delaney) Date: Wed, 13 Mar 2013 11:54:10 +0000 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> Message-ID: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> New submission from Ian Delaney : in the test suite comprising of all of 2 test files, it trips over here test_appe_rest (__main__.TestFtpStoreDataMProcMixin) ... ok test_failing_rest_on_stor (__main__.TestFtpStoreDataMProcMixin) ... ok test_quit_during_transfer (__main__.TestFtpStoreDataMProcMixin) ... ok test_rest_on_stor (__main__.TestFtpStoreDataMProcMixin) ... ^X^C It persistently hangs on (a number of) tests testing stor(age) of data and I have no idea where to start. fijal, you made a package called ctypes_configure who know when. It's been made a dep to tests for pyzmq but I can't add it to portage since it lacks both a live homepage and a license. Plse shoer it up. ---------- assignedto: fijal messages: 5447 nosy: fijal, idella5, pypy-issue priority: performance bug release: 2.0 status: chatting title: pypy latest trips over pyftpdlib-1.0.1 storage related tests ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 14 18:03:53 2013 From: tracker at bugs.pypy.org (Diez B. Roggisch) Date: Thu, 14 Mar 2013 17:03:53 +0000 Subject: [pypy-issue] [issue1422] ROOTSYS required even though docs indicate it isn't In-Reply-To: <1363280633.21.0.593733507373.issue1422@bugs.pypy.org> Message-ID: <1363280633.21.0.593733507373.issue1422@bugs.pypy.org> New submission from Diez B. Roggisch : http://doc.pypy.org/en/latest/cppyy.html states that ROOTSYS is only needed if no root-config utility is available. I have the latter available, but still compilation of pypy failed. After looking into reflex_capi.py it became apparent that ROOTSYS *must* be set. I could provide a doc update or try work on a patch to make docs and reality match. ---------- messages: 5448 nosy: deets, pypy-issue priority: bug status: unread title: ROOTSYS required even though docs indicate it isn't ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 14 19:10:46 2013 From: tracker at bugs.pypy.org (Fijal) Date: Thu, 14 Mar 2013 18:10:46 +0000 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> Message-ID: <1363284646.81.0.756412378882.issue1421@bugs.pypy.org> Fijal added the comment: pyzmq these days depends on cffi (for pypy at least), ctypes_configure should not be used any more. Cheers, fijal ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 14 22:12:14 2013 From: tracker at bugs.pypy.org (Wim Lavrijsen) Date: Thu, 14 Mar 2013 21:12:14 +0000 Subject: [pypy-issue] [issue1422] ROOTSYS required even though docs indicate it isn't In-Reply-To: <1363280633.21.0.593733507373.issue1422@bugs.pypy.org> Message-ID: <1363295534.63.0.50964139183.issue1422@bugs.pypy.org> Wim Lavrijsen added the comment: Should be fixed now and test added in both default and reflex-support branch. Thanks for reporting! ---------- assignedto: -> wlav nosy: +wlav release: -> 2.0 status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 15 09:03:28 2013 From: tracker at bugs.pypy.org (Ian Delaney) Date: Fri, 15 Mar 2013 08:03:28 +0000 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> Message-ID: <1363334608.9.0.738253711741.issue1421@bugs.pypy.org> Ian Delaney added the comment: ak ok, I suppose I have to tease out any tests that dep on ctypes_configure. what of this hanging with the testsuite? Is it something you can fix or those at pyftpdlib should re=write to cater to pypy? ________________________________________ PyPy bug tracker ________________________________________ From fijall at gmail.com Fri Mar 15 17:12:30 2013 From: fijall at gmail.com (Maciej Fijalkowski) Date: Fri, 15 Mar 2013 09:12:30 -0700 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363334608.9.0.738253711741.issue1421@bugs.pypy.org> References: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> <1363334608.9.0.738253711741.issue1421@bugs.pypy.org> Message-ID: On Fri, Mar 15, 2013 at 1:03 AM, Ian Delaney wrote: > > Ian Delaney added the comment: > > ak ok, I suppose I have to tease out any tests that dep on ctypes_configure. > > what of this hanging with the testsuite? Is it something you can fix or those at > pyftpdlib should re=write to cater to pypy? cffi is better these days, I can probably put ctypes_configure website somewhere though. It's pycon now though so later :) From tracker at bugs.pypy.org Fri Mar 15 22:08:30 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Fri, 15 Mar 2013 21:08:30 +0000 Subject: [pypy-issue] [issue1420] _marshal.dump_unicode() - wrong length serialized In-Reply-To: <1363136564.05.0.413392079637.issue1420@bugs.pypy.org> Message-ID: <1363381710.21.0.458097119913.issue1420@bugs.pypy.org> Brian Kearns added the comment: fixed in 6cbb87a9026d, thanks ---------- nosy: +bdk status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 16 20:00:13 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 16 Mar 2013 19:00:13 +0000 Subject: [pypy-issue] [issue1423] performance characteristics of pickle StringBuilder wrapper In-Reply-To: <1363460413.09.0.314542376025.issue1423@bugs.pypy.org> Message-ID: <1363460413.09.0.314542376025.issue1423@bugs.pypy.org> New submission from Brian Kearns : Without changeset 519e4fca15cb, shown below, performance on the following script is 20% worse. Shouldn't they be able to be optimized equally well? Is this a missed optimization? diff --git a/lib-python/2/pickle.py b/lib-python/2/pickle.py --- a/lib-python/2/pickle.py +++ b/lib-python/2/pickle.py @@ -1418,9 +1418,7 @@ ''' def __init__(self): self.builder = StringBuilder() - - def write(self, data): - self.builder.append(data) + self.write = self.builder.append def getvalue(self): return self.builder.build() ------------------------------------------------------- import pickle class Point(object): def __init__(self, x, y): self.x = x self.y = y def test(): n_loops = 200000 N = 2 data = [Point(x, y) for x in xrange(N) for y in xrange(N)] for _ in xrange(n_loops): len(pickle.dumps(data, pickle.HIGHEST_PROTOCOL)) test() ---------- messages: 5454 nosy: bdk, pypy-issue priority: performance bug status: unread title: performance characteristics of pickle StringBuilder wrapper ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 19:53:41 2013 From: tracker at bugs.pypy.org (kostia.lopuhin) Date: Sun, 17 Mar 2013 18:53:41 +0000 Subject: [pypy-issue] [issue1424] A crash in JIT In-Reply-To: <1363546421.44.0.566672029343.issue1424@bugs.pypy.org> Message-ID: <1363546421.44.0.566672029343.issue1424@bugs.pypy.org> New submission from kostia.lopuhin : Attached program crashes freshly translated PyPy (after f82ae0d (fijal, alex): fix a crash in the JIT when memory locations are more than 4GB apart): RPython traceback: File "rpython_jit_metainterp_compile.c", line 20112, in send_bridge_to_backend File "rpython_jit_backend_x86_assembler_1.c", line 13154, in Assembler386_assemble_bridge File "rpython_jit_backend_x86_regalloc.c", line 962, in RegAlloc_walk_operations File "rpython_jit_backend_x86_regalloc.c", line 45003, in RegAlloc_perform_with_guard File "rpython_jit_backend_x86_assembler_1.c", line 7271, in Assembler386_genop_guard_call_assembler File "rpython_jit_backend_llsupport_assembler.c", line 2500, in BaseAssembler_call_assembler File "rpython_jit_backend_x86_assembler_1.c", line 9847, in Assembler386__call_assembler_check_descr File "rpython_jit_backend_x86_rx86.c", line 5825, in INSN__star_3 Fatal RPython error: AssertionError Abort trap: 6 It seems to be an exception here https://bitbucket.org/pypy/pypy/src/ca2784f3146de74a7591bcc1bdc6da8aff7029b1/rpython/jit/metainterp/compile.py?at=default#cl-388 I can reproduce it easily and give additional info ---------- files: bench_pickle.py messages: 5455 nosy: kostia.lopuhin, pypy-issue priority: bug status: unread title: A crash in JIT ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 20:10:06 2013 From: tracker at bugs.pypy.org (kostia.lopuhin) Date: Sun, 17 Mar 2013 19:10:06 +0000 Subject: [pypy-issue] [issue1424] A crash in JIT In-Reply-To: <1363546421.44.0.566672029343.issue1424@bugs.pypy.org> Message-ID: <1363547406.26.0.222156822091.issue1424@bugs.pypy.org> kostia.lopuhin added the comment: forgot to add - this happens on OS X 10.8 ---------- status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 21:28:28 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sun, 17 Mar 2013 20:28:28 +0000 Subject: [pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks In-Reply-To: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> Message-ID: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> New submission from Brian Kearns : $ ./pypy/bin/pyinteractive.py -v PyPy 2.0.0-beta1 in StdObjSpace on top of Python 2.7.3 (startuptime: 10.27 secs) >>>> raise ValueError || Traceback (interpreter-level): || File "./pypy/bin/../../pypy/interpreter/main.py", line 103, in run_toplevel || f() || File "./pypy/bin/../../pypy/interpreter/interactive.py", line 192, in doit || code.exec_code(self.space, self.w_globals, self.w_globals) || File "./pypy/bin/../../pypy/interpreter/eval.py", line 33, in exec_code || return frame.run() || File "./pypy/bin/../../pypy/interpreter/pyframe.py", line 141, in run || return self.execute_frame() || File "./pypy/bin/../../pypy/interpreter/pyframe.py", line 175, in execute_frame || executioncontext) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 81, in dispatch || next_instr = self.handle_bytecode(co_code, next_instr, ec) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 89, in handle_bytecode || next_instr = self.handle_operation_error(ec, operr) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 87, in handle_bytecode || next_instr = self.dispatch_bytecode(co_code, next_instr, ec) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 259, in dispatch_bytecode || res = meth(oparg, next_instr) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 558, in RAISE_VARARGS || raise operror || Traceback (interpreter-level): || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 87, in handle_bytecode || next_instr = self.dispatch_bytecode(co_code, next_instr, ec) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 259, in dispatch_bytecode || res = meth(oparg, next_instr) || File "./pypy/bin/../../pypy/interpreter/pyopcode.py", line 558, in RAISE_VARARGS || raise operror Traceback (application-level): File "", line 1 in raise ValueError (application-level) ValueError >>>> One comes from record_intepreter_traceback in main.py, the other from record_interpreter_traceback in executioncontext.py. Is one redundant? ---------- messages: 5457 nosy: bdk, pypy-issue priority: bug status: unread title: pyinteractive.py -v prints duplicate interpreter-level tracebacks ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 21:32:09 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sun, 17 Mar 2013 20:32:09 +0000 Subject: [pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks In-Reply-To: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> Message-ID: <1363552329.59.0.283250540516.issue1425@bugs.pypy.org> Brian Kearns added the comment: And if you run pyinteractive.py -v file.py containing 'raise ValueError' you get three interpreter-level tracebacks of the same exception... ---------- status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 21:38:04 2013 From: tracker at bugs.pypy.org (Carl Friedrich Bolz) Date: Sun, 17 Mar 2013 20:38:04 +0000 Subject: [pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks In-Reply-To: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> Message-ID: <1363552684.8.0.690970132337.issue1425@bugs.pypy.org> Carl Friedrich Bolz added the comment: That's actually a feature, it can be helpful when debugging where an applevel exception comes from. Didn't find documentation for it though. pyinteractive.py has a few extra features like that: http://doc.pypy.org/en/latest/getting-started-dev.html#special-introspection-features-of-the-untranslated-python-interpreter I've no clue why you get three exceptions in the file case though... ---------- nosy: +cfbolz status: chatting -> ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 21:38:10 2013 From: tracker at bugs.pypy.org (Carl Friedrich Bolz) Date: Sun, 17 Mar 2013 20:38:10 +0000 Subject: [pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks In-Reply-To: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> Message-ID: <1363552690.96.0.701518467068.issue1425@bugs.pypy.org> Carl Friedrich Bolz added the comment: That's actually a feature, it can be helpful when debugging where an applevel exception comes from. Didn't find documentation for it though. pyinteractive.py has a few extra features like that: http://doc.pypy.org/en/latest/getting-started-dev.html#special-introspection-features-of-the-untranslated-python-interpreter I've no clue why you get three exceptions in the file case though... ---------- nosy: +cfbolz ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 21:59:26 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sun, 17 Mar 2013 20:59:26 +0000 Subject: [pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks In-Reply-To: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> Message-ID: <1363553966.21.0.272509378788.issue1425@bugs.pypy.org> Brian Kearns added the comment: Yes, I know printing interpreter level tracebacks is a feature triggered by -v. But look, in each case the same interpreter level exception is recorded multiple (either two or three) times. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 17 22:07:05 2013 From: tracker at bugs.pypy.org (Carl Friedrich Bolz) Date: Sun, 17 Mar 2013 21:07:05 +0000 Subject: [pypy-issue] [issue1425] pyinteractive.py -v prints duplicate interpreter-level tracebacks In-Reply-To: <1363552108.58.0.274808147436.issue1425@bugs.pypy.org> Message-ID: <1363554425.57.0.145647992742.issue1425@bugs.pypy.org> Carl Friedrich Bolz added the comment: Hm, the interplevel tracebacks are weird indeed. The latter ones aren't even full tracebacks, they seem to be getting shorter. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 18 01:47:46 2013 From: tracker at bugs.pypy.org (Sergey Kishchenko) Date: Mon, 18 Mar 2013 00:47:46 +0000 Subject: [pypy-issue] [issue1419] numpypy crash when using bool indices and a different dtype In-Reply-To: <1363086596.6.0.657951887248.issue1419@bugs.pypy.org> Message-ID: <1363567666.69.0.970307150815.issue1419@bugs.pypy.org> Sergey Kishchenko added the comment: I've tried to reproduce the issue on PyPy-1.9.0 and 2.0.0-beta1(3dd4799bc8c3 changeset from the repo) on a linux box (Linux 3.5.2-gentoo #6 SMP) and I can't reproduce the issue. Could you please clarify what's the version of PyPy and OS you have used? ---------- nosy: +tilarids status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 18 20:18:51 2013 From: tracker at bugs.pypy.org (Sergey Kishchenko) Date: Mon, 18 Mar 2013 19:18:51 +0000 Subject: [pypy-issue] [issue1282] Too much memory consumed (looks like severe memory leak) In-Reply-To: <1349776944.1.0.58301608413.issue1282@bugs.pypy.org> Message-ID: <1363634331.13.0.262814568672.issue1282@bugs.pypy.org> Sergey Kishchenko added the comment: It can be two separate issues as far as I can see. Using try..except in generators makes pypy use a lot of memory (70 mb just for arigo's example on my box). But it still doesn't consume more than 70 mb so I can GC is doing fine here. On the other hand, having nesting generator calls from the arigo's example is what's taking pypy on it's knees. On my box def gen1(n): if n > 0: g = gen1(n-1) next(g) yield 5 while 1: next(gen1(100)) consumes 1.5gb RAM in seconds and keeps eating memory until stopped. The same script started through pyinteractive.py uses only 72 MB so I suppose there is the issue with the translated code/translator ---------- nosy: +tilarids ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 18 21:40:59 2013 From: tracker at bugs.pypy.org (kostia.lopuhin) Date: Mon, 18 Mar 2013 20:40:59 +0000 Subject: [pypy-issue] [issue1424] A crash in JIT In-Reply-To: <1363546421.44.0.566672029343.issue1424@bugs.pypy.org> Message-ID: <1363639259.67.0.792264085786.issue1424@bugs.pypy.org> kostia.lopuhin added the comment: Another interesting thing is that the last entry in jit log says smth about loop -1: [338adee5c12] {jit-backend-addr Loop -1 () has address 0x106105ff1 to 0x1061060ce (bootstrap 0x106105f80) [338adee71f5] jit-backend-addr} [338adee8072] {jit-backend-dump BACKEND x86_64 SYS_EXECUTABLE ./pypy-c-jit-default CODE_DUMP @10610606d +0 5D000000 [338adeffc2c] jit-backend-dump} [338ae9f7058] {jit-backend ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 00:59:00 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Mon, 18 Mar 2013 23:59:00 +0000 Subject: [pypy-issue] [issue1282] Too much memory consumed (looks like severe memory leak) In-Reply-To: <1349776944.1.0.58301608413.issue1282@bugs.pypy.org> Message-ID: <1363651140.26.0.875852865491.issue1282@bugs.pypy.org> Amaury Forgeot d Arc added the comment: I see the same "leak" when running in pyinteractive.py. Note hat GeneratorIterator.__del__ "resurrects" the object (through self.enqueue_for_destruction) When interpreted, the effect looks very similar to http://bugs.python.org/issue1540, I wonder if the real PyPy garbage collector can have the same issue. ---------- nosy: +amaury ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 01:30:55 2013 From: tracker at bugs.pypy.org (mattip) Date: Tue, 19 Mar 2013 00:30:55 +0000 Subject: [pypy-issue] [issue1118] numpypy: indexing of 2D arrays with 1-D boolean arrays is broken In-Reply-To: <1333938459.17.0.362001926516.issue1118@bugs.pypy.org> Message-ID: <1363653055.94.0.240492183878.issue1118@bugs.pypy.org> mattip added the comment: fixed on indexing-by-array branch, merged into default eef3ab099ef2 ---------- nosy: +mattip status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 01:36:50 2013 From: tracker at bugs.pypy.org (mattip) Date: Tue, 19 Mar 2013 00:36:50 +0000 Subject: [pypy-issue] [issue1143] numpypy: bug in array_equal In-Reply-To: <1337195357.97.0.624497287196.issue1143@bugs.pypy.org> Message-ID: <1363653410.99.0.873777949435.issue1143@bugs.pypy.org> mattip added the comment: works on default, but this still causes an exception np.array_equal(4, 2) ---------- status: chatting -> in-progress ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 05:58:27 2013 From: tracker at bugs.pypy.org (Fijal) Date: Tue, 19 Mar 2013 04:58:27 +0000 Subject: [pypy-issue] [issue1424] A crash in JIT In-Reply-To: <1363546421.44.0.566672029343.issue1424@bugs.pypy.org> Message-ID: <1363669107.27.0.176388313426.issue1424@bugs.pypy.org> Fijal added the comment: I should have fixed your thing. -1 is the prebuilt loop. ---------- nosy: +fijal ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 07:11:17 2013 From: tracker at bugs.pypy.org (Fijal) Date: Tue, 19 Mar 2013 06:11:17 +0000 Subject: [pypy-issue] [issue1282] Too much memory consumed (looks like severe memory leak) In-Reply-To: <1349776944.1.0.58301608413.issue1282@bugs.pypy.org> Message-ID: <1363673477.52.0.434866319876.issue1282@bugs.pypy.org> Fijal added the comment: there is a branch to deal with that, gc-del ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 08:50:56 2013 From: tracker at bugs.pypy.org (Jimmy Merrild Krag) Date: Tue, 19 Mar 2013 07:50:56 +0000 Subject: [pypy-issue] [issue1426] No way to support PyPy directly through flattr.com In-Reply-To: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> Message-ID: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> New submission from Jimmy Merrild Krag : I generally support things through subscribing to monthly micro donations on flattr.com. That way, anything I support get something every month, instead of just a one time donation. I can easily share things on Flattr, and get more supporters that way. People are just more likely to support stuff on Flattr because of the way the micro donations work. If the cause is good, it's very likely to being subscribed to, and receive monthly donations. ---------- messages: 5470 nosy: beruic, pypy-issue priority: wish status: unread title: No way to support PyPy directly through flattr.com ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 09:02:15 2013 From: tracker at bugs.pypy.org (Fijal) Date: Tue, 19 Mar 2013 08:02:15 +0000 Subject: [pypy-issue] [issue1426] Need a way to support PyPy directly through flattr.com In-Reply-To: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> Message-ID: <1363680135.96.0.53514580511.issue1426@bugs.pypy.org> Fijal added the comment: Hi. We used to have a flattr on our blog (in fact we still do!) and it generates very very little money. In fact, flattr is not intended to work that way - there is no way to sponsor "project", more like "content" etc. If you like what we do, you can sponsor some members of the project on gittip for example. ---------- nosy: +fijal status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 09:07:38 2013 From: tracker at bugs.pypy.org (Jimmy Merrild Krag) Date: Tue, 19 Mar 2013 08:07:38 +0000 Subject: [pypy-issue] [issue1426] Need a way to support PyPy directly through flattr.com In-Reply-To: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> Message-ID: <1363680458.43.0.97462892043.issue1426@bugs.pypy.org> Jimmy Merrild Krag added the comment: Well, there is a software section on flattr. I support (among others) The Document Foundation, libssh and the Debian Package Manager. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 09:42:45 2013 From: tracker at bugs.pypy.org (kostia.lopuhin) Date: Tue, 19 Mar 2013 08:42:45 +0000 Subject: [pypy-issue] [issue1424] A crash in JIT In-Reply-To: <1363546421.44.0.566672029343.issue1424@bugs.pypy.org> Message-ID: <1363682565.36.0.926833533431.issue1424@bugs.pypy.org> kostia.lopuhin added the comment: Yes, the crash is gone, thank you! ---------- status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Tue Mar 19 21:08:08 2013 From: tracker at bugs.pypy.org (Buck Golemon) Date: Tue, 19 Mar 2013 20:08:08 +0000 Subject: [pypy-issue] [issue340] rewrite PyPy's tokenizer In-Reply-To: <1199222224.79.0.545216788228.issue340@> Message-ID: <1363723688.78.0.496225878553.issue340@bugs.pypy.org> Buck Golemon added the comment: Just recording this here for everyone's information. On Mon, Mar 18, 2013 at 10:42 PM, Benjamin Peterson wrote: Hi Buck, I wanted to say a bit more about what a better PyPy tokenizer would look like. If you look in pypy/interpreter/pyparser/pytokenizer.py, you'll see the main rountine is generate_tokens(). I think that routine is fine overall. You'll notice it uses things like "endDFA" and "whiteSpaceDFA" for matching. Looking under the layers, you'll see this is basically a bunch of automatically generated icky DFAs. That would be a excellent place for the regular expressions of rply. ---------- nosy: +buck ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 09:14:42 2013 From: tracker at bugs.pypy.org (Ian Delaney) Date: Wed, 20 Mar 2013 08:14:42 +0000 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> Message-ID: <1363767282.65.0.886584191086.issue1421@bugs.pypy.org> Ian Delaney added the comment: I don't quite follow. ctypes_configure should not be used any more, however you consider re-introducing ctypes_configure to a website, the only package with 'pycon' is pyconstruct which I'd have thought is totally distinct. and pyftpdlib tests re pypy? ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 10:05:53 2013 From: tracker at bugs.pypy.org (Carl Friedrich Bolz) Date: Wed, 20 Mar 2013 09:05:53 +0000 Subject: [pypy-issue] [issue1426] Need a way to support PyPy directly through flattr.com In-Reply-To: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> Message-ID: <1363770353.16.0.35358436341.issue1426@bugs.pypy.org> Carl Friedrich Bolz added the comment: Ok, I added a PyPy thing on flattr: https://flattr.com/thing/1191749 it would be cool if somebody added the necessary html code to pypy.org, maybe the side bar? Flattr this It's actually not true that we earn nothing from Flattr. Not gigantic amounts, but a few euros continuously every month. ---------- nosy: +cfbolz ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 10:12:33 2013 From: tracker at bugs.pypy.org (Jimmy Merrild Krag) Date: Wed, 20 Mar 2013 09:12:33 +0000 Subject: [pypy-issue] [issue1426] Need a way to support PyPy directly through flattr.com In-Reply-To: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> Message-ID: <1363770753.48.0.0759061591078.issue1426@bugs.pypy.org> Jimmy Merrild Krag added the comment: Well, you just got your first subscriber, and it all adds up :) Little strokes fell great oaks. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 12:06:01 2013 From: tracker at bugs.pypy.org (Carl Friedrich Bolz) Date: Wed, 20 Mar 2013 11:06:01 +0000 Subject: [pypy-issue] [issue340] rewrite PyPy's tokenizer In-Reply-To: <1199222224.79.0.545216788228.issue340@> Message-ID: <1363777561.61.0.553431788099.issue340@bugs.pypy.org> Carl Friedrich Bolz added the comment: I am not really sure that using rply's tokenizer would improve things (I should really raise that with Alex, too). rply's tokenizer uses rlib.rsre to tokenize stuff, which is overkill, given that the regular expressions needed for Python's tokens are really regular, not Perl-style regular expressions. ---------- nosy: +cfbolz ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 18:46:39 2013 From: tracker at bugs.pypy.org (Fijal) Date: Wed, 20 Mar 2013 17:46:39 +0000 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> Message-ID: <1363801599.66.0.0718779155809.issue1421@bugs.pypy.org> Fijal added the comment: ctypes_configure should not be used, but it does not mean it should not have a website (it won't be endorsed on the pypy website though) as for pycon - it's a conference we're all attending so response times are slow :) ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 20:43:53 2013 From: tracker at bugs.pypy.org (mattip) Date: Wed, 20 Mar 2013 19:43:53 +0000 Subject: [pypy-issue] [issue1427] numpypy test coverage In-Reply-To: <1363808633.97.0.143069813677.issue1427@bugs.pypy.org> Message-ID: <1363808633.97.0.143069813677.issue1427@bugs.pypy.org> New submission from mattip : We do not have 100% code coverage when running pypy/test_all.py --cov pypy/module/micronumpy pypy/module/micronumpy/test --cov- report=html Many corner cases raise exceptions but these are never tested ---------- messages: 5480 nosy: mattip, pypy-issue priority: bug status: unread title: numpypy test coverage ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Wed Mar 20 20:45:33 2013 From: tracker at bugs.pypy.org (mattip) Date: Wed, 20 Mar 2013 19:45:33 +0000 Subject: [pypy-issue] [issue1143] numpypy: bug in array_equal In-Reply-To: <1337195357.97.0.624497287196.issue1143@bugs.pypy.org> Message-ID: <1363808733.67.0.0347691675705.issue1143@bugs.pypy.org> mattip added the comment: fixed scalar case ---------- status: in-progress -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 08:47:35 2013 From: tracker at bugs.pypy.org (Ian Delaney) Date: Thu, 21 Mar 2013 07:47:35 +0000 Subject: [pypy-issue] [issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests In-Reply-To: <1363175650.76.0.196546286513.issue1421@bugs.pypy.org> Message-ID: <1363852055.6.0.0869673469702.issue1421@bugs.pypy.org> Ian Delaney added the comment: ah, a conference, I see. I filed at pyzmq and a maintainer there has sorted it out and removed ctypes_configure seemingly from my prompt since your ctypes_configure was hardcode imported in a core module. ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 14:48:38 2013 From: tracker at bugs.pypy.org (George Sakkis) Date: Thu, 21 Mar 2013 13:48:38 +0000 Subject: [pypy-issue] [issue1428] PyLong_FromUnicode seems to return int instead of long In-Reply-To: <1363873718.56.0.438633499695.issue1428@bugs.pypy.org> Message-ID: <1363873718.56.0.438633499695.issue1428@bugs.pypy.org> New submission from George Sakkis : I am using jsonlib for parsing json and ran into a subtle difference between cPython and PyPy: >>> import jsonlib >>> jsonlib.loads("[1]") [1L] >>>> import jsonlib >>>> jsonlib.loads("[1]") [1] The related code calls PyLong_FromUnicode [1] so wondering why PyPy returns an int instead. [1] http://bazaar.launchpad.net/~jmillikin/jsonlib/python3/view/head:/_jsonlib.c#L663 ---------- messages: 5483 nosy: gsakkis, pypy-issue priority: bug status: unread title: PyLong_FromUnicode seems to return int instead of long ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 15:23:51 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Thu, 21 Mar 2013 14:23:51 +0000 Subject: [pypy-issue] [issue1428] PyLong_FromUnicode seems to return int instead of long In-Reply-To: <1363873718.56.0.438633499695.issue1428@bugs.pypy.org> Message-ID: <1363875831.45.0.814662906242.issue1428@bugs.pypy.org> Amaury Forgeot d Arc added the comment: PyPy does not define the PyLong_FromUnicode() function, so you are probably using the pure-Python version of jsonlib. Indeed, in jsonlib.py the function read_number() has a line that says:: int_part = int (match.group ('int'), 10) ---------- nosy: +amaury status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 15:41:36 2013 From: tracker at bugs.pypy.org (mrjbq7) Date: Thu, 21 Mar 2013 14:41:36 +0000 Subject: [pypy-issue] [issue1429] CSV module is slow In-Reply-To: <1363876896.88.0.901114514497.issue1429@bugs.pypy.org> Message-ID: <1363876896.88.0.901114514497.issue1429@bugs.pypy.org> New submission from mrjbq7 : Using the 6.7MB airport.csv file from ourairports.com (http://www.ourairports.com/data/airports.csv) saved to "/tmp/airports.csv", and the attached python script (csvtest.py). On Python 2.7.2: reading took 0.137 seconds writing took 0.126 seconds complete took 0.264 seconds On PyPy 1.9.0: reading took 0.627 seconds writing took 0.491 seconds complete took 1.118 seconds ---------- messages: 5485 nosy: mrjbq7, pypy-issue priority: performance bug status: unread title: CSV module is slow ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 16:10:28 2013 From: tracker at bugs.pypy.org (George Sakkis) Date: Thu, 21 Mar 2013 15:10:28 +0000 Subject: [pypy-issue] [issue1428] PyLong_FromUnicode seems to return int instead of long In-Reply-To: <1363873718.56.0.438633499695.issue1428@bugs.pypy.org> Message-ID: <1363878628.89.0.0988303811903.issue1428@bugs.pypy.org> George Sakkis added the comment: Thanks for the quick reply, I didn't it falls back to the pure Python version. ---------- status: chatting -> invalid ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 18:11:00 2013 From: tracker at bugs.pypy.org (Amaury Forgeot d Arc) Date: Thu, 21 Mar 2013 17:11:00 +0000 Subject: [pypy-issue] [issue1429] CSV module is slow In-Reply-To: <1363876896.88.0.901114514497.issue1429@bugs.pypy.org> Message-ID: <1363885860.67.0.392337405772.issue1429@bugs.pypy.org> Amaury Forgeot d Arc added the comment: 1.9 is a bit old already. More recent versions are considerably faster (4x for me for the given script) Can you try with 2.0 beta or a nightly build? ---------- nosy: +amaury status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Thu Mar 21 18:17:13 2013 From: tracker at bugs.pypy.org (mrjbq7) Date: Thu, 21 Mar 2013 17:17:13 +0000 Subject: [pypy-issue] [issue1429] CSV module is slow In-Reply-To: <1363876896.88.0.901114514497.issue1429@bugs.pypy.org> Message-ID: <1363886233.16.0.785198420565.issue1429@bugs.pypy.org> mrjbq7 added the comment: Ok, much better! PyPy nightly build (pypy-c-jit-61334-6bf80dae95f7-osx64): reading took 0.201 seconds writing took 0.129 seconds complete took 0.330 seconds PyPy 2.0-beta1: reading took 0.317 seconds writing took 0.141 seconds complete took 0.458 seconds Reading is still a bit slower than Python 2.7, but you could probably close this bug since the difference is small... thank you (and sorry for not testing on a more recent build)! ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 22 12:57:23 2013 From: tracker at bugs.pypy.org (Vasily Evseenko) Date: Fri, 22 Mar 2013 11:57:23 +0000 Subject: [pypy-issue] [issue1430] Memory corruption on socket.gethostbyname_ex In-Reply-To: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> Message-ID: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> New submission from Vasily Evseenko : There are some memory corruption while calling socket.gethostbyname_ex from the thread while other thread executes JIT'ed code: In such case socket.gethostbyname_ex returns random entries from /etc/hosts instead of DNS lookup. Notes from dev-list: --- - it reproduces even without a JIT-enabled pypy - PyPy uses gethostbyname() instead of gethostbyname_r() --- Affected versions: PyPy 1.8, 1.9, 2.0b1 on Linux (Fedora 16, Debian GNU/Linux 6.0) --- Python 2.7.3 (07e08e9c885ca67d89bcc304e45a32346daea2fa, Mar 19 2013, 07:39:19) [PyPy 2.0.0-beta1 with GCC 4.4.5] on linux2 Python 2.7.3 (07e08e9c885ca67d89bcc304e45a32346daea2fa, Dec 18 2012, 05:33:54) [PyPy 2.0.0-beta1 with GCC 4.6.3] on linux2 Python 2.7.2 (2346207d99463f299f09f3e151c9d5fa9158f71b, May 15 2012, 11:08:08) [PyPy 1.8.0 with GCC 4.6.3] on linux2 Python 2.7.2 (341e1e3821fff77db3bb5cdb7a4851626298c44e, Oct 23 2012, 11:37:42) [PyPy 1.9.0 with GCC 4.6.3] on linux2 --- Not affected: PyPy 2.0b1 on MacOSX --- Python 2.7.3 (07e08e9c885ca67d89bcc304e45a32346daea2fa, Mar 19 2013, 07:52:27) [PyPy 2.0.0-beta1] on darwin Python 2.7.3 (7e4f0faa3d51, Nov 21 2012, 15:59:46) [PyPy 2.0.0-beta1 with GCC 4.2.1] on darwin --- ---------- files: test.py messages: 5489 nosy: pypy-issue, svpcom priority: critical release: 2.0 status: unread title: Memory corruption on socket.gethostbyname_ex ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 22 13:00:43 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Fri, 22 Mar 2013 12:00:43 +0000 Subject: [pypy-issue] [issue1430] Memory corruption on socket.gethostbyname_ex In-Reply-To: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> Message-ID: <1363953643.75.0.811575579078.issue1430@bugs.pypy.org> Brian Kearns added the comment: this is known -- documented in XXX comments in rpython/rlib/rsocket.py. ---------- nosy: +bdk status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 22 13:14:57 2013 From: tracker at bugs.pypy.org (Vasily Evseenko) Date: Fri, 22 Mar 2013 12:14:57 +0000 Subject: [pypy-issue] [issue1430] Memory corruption on socket.gethostbyname_ex In-Reply-To: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> Message-ID: <1363954497.8.0.81536259415.issue1430@bugs.pypy.org> Vasily Evseenko added the comment: Are there any way to convert DNS name to list of ip-addresses without external locks on PyPy? ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 22 13:20:59 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Fri, 22 Mar 2013 12:20:59 +0000 Subject: [pypy-issue] [issue1430] Memory corruption on socket.gethostbyname_ex In-Reply-To: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> Message-ID: <1363954859.18.0.149653225943.issue1430@bugs.pypy.org> Brian Kearns added the comment: try socket.getaddrinfo? ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 22 13:26:24 2013 From: tracker at bugs.pypy.org (Vasily Evseenko) Date: Fri, 22 Mar 2013 12:26:24 +0000 Subject: [pypy-issue] [issue1430] Memory corruption on socket.gethostbyname_ex In-Reply-To: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> Message-ID: <1363955184.31.0.413541076315.issue1430@bugs.pypy.org> Vasily Evseenko added the comment: Thanks a lot! ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 08:22:40 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 07:22:40 +0000 Subject: [pypy-issue] [issue1070] Cpython 2.7 is faster than Pypy on program using Pickle and Sqlite In-Reply-To: <1330238255.79.0.201539943332.issue1070@bugs.pypy.org> Message-ID: <1364023360.15.0.775643815847.issue1070@bugs.pypy.org> Brian Kearns added the comment: Please try again with latest nightly-- I've made several optimizations to sqlite and code supporting pickle. ---------- nosy: +bdk status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 08:42:50 2013 From: tracker at bugs.pypy.org (mikefc) Date: Sat, 23 Mar 2013 07:42:50 +0000 Subject: [pypy-issue] [issue1419] numpypy crash when using bool indices and a different dtype In-Reply-To: <1363086596.6.0.657951887248.issue1419@bugs.pypy.org> Message-ID: <1364024570.51.0.570872718724.issue1419@bugs.pypy.org> mikefc added the comment: No crash on latest OSX nightly. But the latest OSX nightly is from Mid-Feb apparently, so that might help set a lower bound on the time the bug was introduced. ---------- nosy: +mikefc ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 08:43:47 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 07:43:47 +0000 Subject: [pypy-issue] [issue868] Pypy json.dumps >100% slower than CPython 2.7, simplejson In-Reply-To: <1315673548.25.0.59851723037.issue868@bugs.pypy.org> Message-ID: <1364024627.5.0.677232921742.issue868@bugs.pypy.org> Brian Kearns added the comment: Took a look at this again. We do better, but still 'break down' on the HUGE case. $ python2.7 bench.py Test case: EMPTY loops per run 308000 Best performances: 3.25 usec/loop Test case: SIMPLE loops per run 184000 Best performances: 5.49 usec/loop Test case: NESTED loops per run 98000 Best performances: 10.25 usec/loop Test case: HUGE loops per run 1000 Best performances: 2873.16 usec/loop $ ../../pypy/pypy-c bench.py Test case: EMPTY loops per run 1451320 Best performances: 0.03 usec/loop Test case: SIMPLE loops per run 156740 Best performances: 2.20 usec/loop Test case: NESTED loops per run 93110 Best performances: 10.18 usec/loop Test case: HUGE loops per run 180 Best performances: 57414.41 usec/loop ---------- nosy: +bdk ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 08:49:44 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 07:49:44 +0000 Subject: [pypy-issue] [issue979] Pickle fails in pypy, works in CPython In-Reply-To: <1325694743.04.0.41876802496.issue979@bugs.pypy.org> Message-ID: <1364024984.7.0.963702662612.issue979@bugs.pypy.org> Brian Kearns added the comment: this has been fixed in the latest nightly. ---------- nosy: +bdk status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 08:56:33 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 07:56:33 +0000 Subject: [pypy-issue] [issue1419] numpypy crash when using bool indices and a different dtype In-Reply-To: <1363086596.6.0.657951887248.issue1419@bugs.pypy.org> Message-ID: <1364025393.69.0.519004251846.issue1419@bugs.pypy.org> Brian Kearns added the comment: also cannot reproduce with latest nightly, assuming this was fixed, if someone reproduces with latest nightly, reopen this. ---------- nosy: +bdk status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 08:56:53 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 07:56:53 +0000 Subject: [pypy-issue] [issue1431] aurora is back; please connect back win32 nightlies In-Reply-To: <1363983499.84.0.503101084286.issue1431@bugs.pypy.org> Message-ID: <1364025413.61.0.845881029455.issue1431@bugs.pypy.org> Brian Kearns added the comment: they are connected? ---------- nosy: +bdk status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 09:05:35 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 08:05:35 +0000 Subject: [pypy-issue] [issue973] interpreter/test/test_main.py fails when run on pypy-c In-Reply-To: <1324926496.61.0.413500008541.issue973@bugs.pypy.org> Message-ID: <1364025935.24.0.221279528965.issue973@bugs.pypy.org> Brian Kearns added the comment: works fine with latest nightly. ---------- nosy: +bdk status: unread -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 09:38:11 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Sat, 23 Mar 2013 08:38:11 +0000 Subject: [pypy-issue] [issue973] interpreter/test/test_main.py fails when run on pypy-c In-Reply-To: <1324926496.61.0.413500008541.issue973@bugs.pypy.org> Message-ID: <1364027891.63.0.700289894987.issue973@bugs.pypy.org> Brian Kearns added the comment: although even with the latest nightly, if you hg up 38f19c2a15e5, python can run pytest test_main but pypy-c fails. maybe still worth looking at? the first commit to change the situation is the next, d1e21127b822 (first stab at kill-faking). ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 16:09:43 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Sat, 23 Mar 2013 15:09:43 +0000 Subject: [pypy-issue] [issue1426] Need a way to support PyPy directly through flattr.com In-Reply-To: <1363679456.88.0.54853741324.issue1426@bugs.pypy.org> Message-ID: <1364051383.2.0.215395640342.issue1426@bugs.pypy.org> Armin Rigo added the comment: Added in the source code. I cannot log any more to pypy at pypy.org... ---------- nosy: +arigo status: chatting -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sat Mar 23 16:22:45 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Sat, 23 Mar 2013 15:22:45 +0000 Subject: [pypy-issue] [issue629] "Cannot find gc roots" messages on Linux In-Reply-To: <1296343807.1.0.373645133691.issue629@> Message-ID: <1364052165.84.0.920659041675.issue629@bugs.pypy.org> Armin Rigo added the comment: Closing this as "resolved" because victorg5's original problem was resolved. klankschap's issue is still open, but might be gone by now: we changed the world with the jit-frame-in-heap branch, which might have solved the problem. I ran http://bpaste.net/show/85890/ on 9f1099167f6a successfully on an 8-core Linux64, a dozen times. ---------- status: in-progress -> resolved ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 25 04:48:06 2013 From: tracker at bugs.pypy.org (mrjbq7) Date: Mon, 25 Mar 2013 03:48:06 +0000 Subject: [pypy-issue] [issue1432] set(xrange(n)) is slower than set(range(n)) In-Reply-To: <1364183286.46.0.589930482359.issue1432@bugs.pypy.org> Message-ID: <1364183286.46.0.589930482359.issue1432@bugs.pypy.org> New submission from mrjbq7 : Using this test script: ``` import time t0 = time.time() s1 = set() for i in xrange(5000000): s1.add(i) t1 = time.time() s2 = set(xrange(5000000)) t2 = time.time() s3 = set(range(5000000)) t3 = time.time() print 'add one took %.3f seconds' % (t1-t0) print 'add all xrange took %.3f seconds' % (t2-t1) print 'add all range took %.3f seconds' % (t3-t2) ``` The performance on a recently nightly build is: ``` $ ./pypy-c-jit-61334-6bf80dae95f7-osx64/bin/pypy baz.py add one took 0.189 seconds add all xrange took 0.419 seconds add all range took 0.207 seconds ``` ---------- messages: 5505 nosy: mrjbq7, pypy-issue priority: performance bug status: unread title: set(xrange(n)) is slower than set(range(n)) ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 25 14:15:58 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Mon, 25 Mar 2013 13:15:58 +0000 Subject: [pypy-issue] [issue1432] set(xrange(n)) is slower than set(range(n)) In-Reply-To: <1364183286.46.0.589930482359.issue1432@bugs.pypy.org> Message-ID: <1364217358.85.0.284773134263.issue1432@bugs.pypy.org> Brian Kearns added the comment: xrange is also slower in min/max for example. list(xrange(n)) should also be able to be as fast as range(n), and it isn't. one optimization would be for listview on an xrange object or xrange iterator to return a RangeList instead of going through unpackiterable on the xrange. another optimization is for set creation from iterable to get a jitdriver like list extend. ---------- nosy: +bdk status: unread -> chatting ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Mon Mar 25 14:25:38 2013 From: tracker at bugs.pypy.org (Brian Kearns) Date: Mon, 25 Mar 2013 13:25:38 +0000 Subject: [pypy-issue] [issue1433] tuple/list creation is very slow in some cases In-Reply-To: <1364217938.74.0.131530489669.issue1433@bugs.pypy.org> Message-ID: <1364217938.74.0.131530489669.issue1433@bugs.pypy.org> New submission from Brian Kearns : $ python -m timeit -n 10000 -s "a = '1'*5000" "tuple(a)" 10000 loops, best of 3: 47.3 usec per loop $ ./pypy-c -m timeit -n 10000 -s "a = '1'*5000" "tuple(a)" 10000 loops, best of 3: 129 usec per loop $ python -m timeit -n 10000 -s "a = '1'*5000" "list(a)" 10000 loops, best of 3: 48.2 usec per loop $ ./pypy-c -m timeit -n 10000 -s "a = '1'*5000" "list(a)" 10000 loops, best of 3: 157 usec per loop ---------- messages: 5507 nosy: bdk, pypy-issue priority: performance bug status: unread title: tuple/list creation is very slow in some cases ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Fri Mar 29 18:27:23 2013 From: tracker at bugs.pypy.org (Christoph Reiter) Date: Fri, 29 Mar 2013 17:27:23 +0000 Subject: [pypy-issue] [issue1434] CPyExt errors with PyGObject In-Reply-To: <1364578043.09.0.242390855942.issue1434@bugs.pypy.org> Message-ID: <1364578043.09.0.242390855942.issue1434@bugs.pypy.org> New submission from Christoph Reiter : For future reference (since I've given up for now): - Checkout PyGObject git (I've tested 3.4/3.8, 3.4 has lower glib/gir dependencies if that's a problem) - Apply the following patches to make autotools work with PyPy: - https://bugzilla.gnome.org/show_bug.cgi?id=696646 - https://bugzilla.gnome.org/show_bug.cgi?id=696648 - https://bugzilla.gnome.org/show_bug.cgi?id=696650 - Apply the attached patch that works around some limitations in cpyext. - Run the following to build against PyPy (a nightly build for example): PYTHON=/path_to_pypy/bin/pypy ./autogen.sh make - To run the tests: make check or better: SKIP_PEP8=1 make check.gdb (since it segfaults and pep8 tests are slow) The first segfault is because baseclass.tp_new(subclass, ...) # baseclass != subclass doesn't seem to work. ---------- files: pygobject-pypy-fix-v1.patch messages: 5508 nosy: lazka, pypy-issue priority: bug status: unread title: CPyExt errors with PyGObject ________________________________________ PyPy bug tracker ________________________________________ From tracker at bugs.pypy.org Sun Mar 31 18:48:53 2013 From: tracker at bugs.pypy.org (Armin Rigo) Date: Sun, 31 Mar 2013 16:48:53 +0000 Subject: [pypy-issue] [issue1430] Memory corruption on socket.gethostbyname_ex In-Reply-To: <1363953443.4.0.713767024147.issue1430@bugs.pypy.org> Message-ID: <1364748533.01.0.732800424592.issue1430@bugs.pypy.org> Armin Rigo added the comment: How about fixing the XXXes? Grep for USE_GETHOSTBYNAME_LOCK and USE_GETADDRINFO_LOCK in Module/socketmodule.c from CPython. ---------- nosy: +arigo ________________________________________ PyPy bug tracker ________________________________________