From pypy-dev-issue at codespeak.net Tue Mar 23 18:24:30 2010 From: pypy-dev-issue at codespeak.net (PyPy development tracker) Date: Tue, 23 Mar 2010 17:24:30 +0000 Subject: [PyPy-issue] Complete your registration to PyPy development tracker -- key FZ2rWcty7hqZX1Ao2E0fKFIb7RijyUFA Message-ID: <20100323172431.0D79C282BD6@codespeak.net> To complete your registration of the user "pypy-issue" with PyPy development tracker, please do one of the following: - send a reply to pypy-dev-issue at codespeak.net and maintain the subject line as is (the reply's additional "Re:" is ok), - or visit the following URL: https://codespeak.net/issue/pypy-dev/?@action=confrego&otk=FZ2rWcty7hqZX1Ao2E0fKFIb7RijyUFA From pypy-dev-issue at codespeak.net Tue Mar 23 18:34:11 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 23 Mar 2010 17:34:11 +0000 Subject: [PyPy-issue] [issue509] __float__ method not called in cmath Message-ID: <1269365651.19.0.453683926497.issue509@> Armin Rigo added the comment: (sorry, another try...) _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 23 18:59:21 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 23 Mar 2010 17:59:21 +0000 Subject: [PyPy-issue] [issue483] UnpackValueError Message-ID: <1269367161.41.0.34501508483.issue483@> Armin Rigo added the comment: (sorry, trying still to make it work...) ---------- nosy: +benjamin, fijal, pypy-issue _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 23 19:07:34 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 23 Mar 2010 18:07:34 +0000 Subject: [PyPy-issue] [issue483] UnpackValueError Message-ID: <1269367654.74.0.591149983997.issue483@> Armin Rigo added the comment: (sight, confusing) _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 23 19:10:47 2010 From: pypy-dev-issue at codespeak.net (Alex Gaynor) Date: Tue, 23 Mar 2010 18:10:47 +0000 Subject: [PyPy-issue] [issue514] Django tests fail (UnboundLocalError) or segfault Message-ID: <1269367847.72.0.345725551646.issue514@> New submission from Alex Gaynor : I can reproduce this reliably on trunk (compiled with JIT), and 1.2, by doing pypy-c test/runtest.py -v1 --failfast admin_views. ---------- effort: ??? messages: 1671 nosy: ac, agaynor, arigo, benjamin, cfbolz, fijal, hpk, mwh, pedronis, pypy-issue, tismer priority: bug release: ??? status: unread title: Django tests fail (UnboundLocalError) or segfault _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 23 19:14:27 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 23 Mar 2010 18:14:27 +0000 Subject: [PyPy-issue] [issue484] review listview() Message-ID: <1269368067.15.0.646566941317.issue484@> Armin Rigo added the comment: (this is to try out pypy-issue...) ---------- nosy: +benjamin, fijal, pypy-issue status: unread -> chatting _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 23 19:31:03 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 23 Mar 2010 18:31:03 +0000 Subject: [PyPy-issue] [issue413] zipfile.py bugs in 2.5.1/2.5.2 Message-ID: <1269369063.59.0.186107847035.issue413@> Armin Rigo added the comment: (testing the autonosiness of pypy-issue...) ---------- nosy: +pypy-issue -ac, arigo, cfbolz, mwh, pedronis, tismer status: unread -> chatting _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Mon Mar 29 21:34:07 2010 From: pypy-dev-issue at codespeak.net (Fijal) Date: Mon, 29 Mar 2010 19:34:07 +0000 Subject: [PyPy-issue] [issue514] Django tests fail (UnboundLocalError) or segfault Message-ID: <1269891247.24.0.542208259008.issue514@> Fijal added the comment: Works for me... ---------- nosy: -ac, arigo, benjamin, cfbolz, fijal, mwh, pedronis, tismer status: unread -> chatting _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Mon Mar 29 23:01:06 2010 From: pypy-dev-issue at codespeak.net (Fijal) Date: Mon, 29 Mar 2010 21:01:06 +0000 Subject: [PyPy-issue] [issue514] Django tests fail (UnboundLocalError) or segfault Message-ID: <1269896466.37.0.517947695844.issue514@> Fijal added the comment: Ok, I think I found the reason. _assemble in backend/x86/assembler.py can recursively call itself. I have no clue yet *why* and *how* but I'm looking. Leaving this message so I don't forget. (Oh and btw, it's obviously not recursion-safe). _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 30 00:42:40 2010 From: pypy-dev-issue at codespeak.net (Benjamin Peterson) Date: Mon, 29 Mar 2010 22:42:40 +0000 Subject: [PyPy-issue] [issue130] polish object space initialisation Message-ID: <1269902560.45.0.467356552784.issue130@> Benjamin Peterson added the comment: Resolved in r73147. ---------- nosy: +pypy-issue -arigo, cfbolz, pedronis, tismer status: unread -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 30 06:23:45 2010 From: pypy-dev-issue at codespeak.net (Fijal) Date: Tue, 30 Mar 2010 04:23:45 +0000 Subject: [PyPy-issue] [issue514] Django tests fail (UnboundLocalError) or segfault Message-ID: <1269923025.74.0.0258116927113.issue514@> Fijal added the comment: Fixed in 73156 and 73157 ---------- status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 30 11:42:03 2010 From: pypy-dev-issue at codespeak.net (Matteo Bertini) Date: Tue, 30 Mar 2010 09:42:03 +0000 Subject: [PyPy-issue] [issue515] __future__ import fails (silently) if after a r"string" Message-ID: <1269942123.06.0.226993187357.issue515@> New submission from Matteo Bertini : [11:35] matteo at spovest:~/Downloads/pypy-1.2-osx$ python2.5 with1.py """ something """ from __future__ import with_statement with open(__file__) as stream: print "".join(stream) [11:35] matteo at spovest:~/Downloads/pypy-1.2-osx$ python2.5 with2.py r""" something """ from __future__ import with_statement with open(__file__) as stream: print "".join(stream) [11:35] matteo at spovest:~/Downloads/pypy-1.2-osx$ pypy with1.py """ something """ from __future__ import with_statement with open(__file__) as stream: print "".join(stream) [11:35] matteo at spovest:~/Downloads/pypy-1.2-osx$ pypy with2.py Traceback (most recent call last): File "?", line 33, in run_toplevel File "with2.py", line 7 with open(__file__) as stream: ^ SyntaxError: invalid syntax ---------- effort: ??? messages: 1678 nosy: hpk, naufraghi, pypy-issue priority: bug release: ??? status: unread title: __future__ import fails (silently) if after a r"string" _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 30 15:09:20 2010 From: pypy-dev-issue at codespeak.net (Antoine P) Date: Tue, 30 Mar 2010 13:09:20 +0000 Subject: [PyPy-issue] [issue516] Fix special method choice algorithm for old-style classes Message-ID: <1269954560.28.0.124132368705.issue516@> New submission from Antoine P : exarkun pointed me to the following failure on the twisted pypy buildbot: (from http://buildbot.twistedmatrix.com/builders/ubuntu32-pypy/builds/144/steps/trial/logs/problems ) =============================================================================== [FAIL]: twisted.python.test.test_util.EqualityTests.test_inheritedClassesEquality Traceback (most recent call last): File "/var/lib/buildbot/twisted-bigdogvm1/ubuntu32-pypy/build/Twisted-src/twisted/python/test/test_util.py", line 578, in test_inheritedClassesEquality self.assertTrue(Record(1, 2) == DerivedRecord(1, 2)) twisted.trial.unittest.FailTest: None =============================================================================== [FAIL]: twisted.python.test.test_util.EqualityTests.test_inheritedClassesInequality Traceback (most recent call last): File "/var/lib/buildbot/twisted-bigdogvm1/ubuntu32-pypy/build/Twisted-src/twisted/python/test/test_util.py", line 590, in test_inheritedClassesInequality self.assertFalse(Record(1, 2) != DerivedRecord(1, 2)) twisted.trial.unittest.FailTest: None Here is a patch. ---------- effort: ??? files: oldstyle-descr2.patch messages: 1679 nosy: hpk, pitrou, pypy-issue priority: bug release: ??? status: in-progress title: Fix special method choice algorithm for old-style classes _______________________________________________________ PyPy development tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: oldstyle-descr2.patch Type: text/x-diff Size: 10413 bytes Desc: not available URL: From pypy-dev-issue at codespeak.net Tue Mar 30 16:11:41 2010 From: pypy-dev-issue at codespeak.net (Antoine P) Date: Tue, 30 Mar 2010 14:11:41 +0000 Subject: [PyPy-issue] [issue516] Fix special method choice algorithm for old-style classes Message-ID: <1269958301.3.0.430117925705.issue516@> Antoine P added the comment: The patch didn't pass translation, this one does. It also passes all tests in interpreter/, objspace/ and module/__builtin__/ (thanks cfbolz for helping!) _______________________________________________________ PyPy development tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: oldstyle-descr3.patch Type: text/x-diff Size: 10891 bytes Desc: not available URL: From pypy-dev-issue at codespeak.net Tue Mar 30 16:18:42 2010 From: pypy-dev-issue at codespeak.net (Carl Friedrich Bolz) Date: Tue, 30 Mar 2010 14:18:42 +0000 Subject: [PyPy-issue] [issue516] Fix special method choice algorithm for old-style classes Message-ID: <1269958722.53.0.0420273606212.issue516@> Carl Friedrich Bolz added the comment: Modified: pypy/trunk/pypy/objspace/descroperation.py pypy/trunk/pypy/objspace/test/test_descroperation.py Log: issue516 resolved (Antoine Pitrou) Fix special method choice algorithm for old-style classes _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Mar 30 16:54:54 2010 From: pypy-dev-issue at codespeak.net (Benjamin Peterson) Date: Tue, 30 Mar 2010 14:54:54 +0000 Subject: [PyPy-issue] [issue515] __future__ import fails (silently) if after a r"string" Message-ID: <1269960894.36.0.938214924498.issue515@> Benjamin Peterson added the comment: Fixed in r73173. ---------- status: unread -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________