From pypy-dev-issue at codespeak.net Mon Aug 2 19:25:56 2010 From: pypy-dev-issue at codespeak.net (hruske) Date: Mon, 02 Aug 2010 17:25:56 +0000 Subject: [PyPy-issue] [issue466] ctypes: False -> c_char_p argument Message-ID: <1280769956.43.0.664494291795.issue466@> hruske added the comment: Fixed in r76381. ---------- nosy: +pypy-issue -ac, arigo, cfbolz, mwh, pedronis, tismer status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 10 08:24:09 2010 From: pypy-dev-issue at codespeak.net (Fijal) Date: Tue, 10 Aug 2010 06:24:09 +0000 Subject: [PyPy-issue] [issue552] crash in JIT Message-ID: <1281421449.83.0.357035603898.issue552@> Fijal added the comment: I didn't try so far. Might try sometime soon, but no promises _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 10 12:32:40 2010 From: pypy-dev-issue at codespeak.net (Antonio Cuni) Date: Tue, 10 Aug 2010 10:32:40 +0000 Subject: [PyPy-issue] [issue355] wrong sys.(exec_prefix) from translating python Message-ID: <1281436360.48.0.574639354888.issue355@> Antonio Cuni added the comment: solved by r75556, i.e. merging of the "sys-prefix" branch ---------- nosy: +pypy-issue -ac, arigo, cfbolz, mwh, pedronis, tismer status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 10 12:33:43 2010 From: pypy-dev-issue at codespeak.net (Antonio Cuni) Date: Tue, 10 Aug 2010 10:33:43 +0000 Subject: [PyPy-issue] [issue505] site.py in local directory imported on startup. Message-ID: <1281436423.66.0.114258199864.issue505@> Antonio Cuni added the comment: solved by r76361 ---------- status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Fri Aug 13 11:22:13 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Fri, 13 Aug 2010 09:22:13 +0000 Subject: [PyPy-issue] [issue552] crash in JIT Message-ID: <1281691333.47.0.963289095712.issue552@> Armin Rigo added the comment: Fixed (r76582). ---------- status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Thu Aug 19 16:13:42 2010 From: pypy-dev-issue at codespeak.net (Tanel Liiv) Date: Thu, 19 Aug 2010 14:13:42 +0000 Subject: [PyPy-issue] [issue554] main thread not calling threading.shutdown() when exiting Message-ID: <1282227222.85.0.982691511367.issue554@> New submission from Tanel Liiv : The main thread doesn't wait for child threads to finish before exiting. ---------- assignedto: kuratkull effort: easy files: stress2.py messages: 1814 nosy: kuratkull, pypy-issue priority: bug release: ??? status: unread title: main thread not calling threading.shutdown() when exiting _______________________________________________________ PyPy development tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: stress2.py Type: text/x-python Size: 127 bytes Desc: not available URL: From pypy-dev-issue at codespeak.net Thu Aug 19 16:16:20 2010 From: pypy-dev-issue at codespeak.net (Tanel Liiv) Date: Thu, 19 Aug 2010 14:16:20 +0000 Subject: [PyPy-issue] [issue554] main thread not calling threading._shutdown() when exiting Message-ID: <1282227380.49.0.478906867803.issue554@> Tanel Liiv added the comment: CPython calls threading._shutdown() on exit argh, there is a "test_1_join_on_shutdown()" in test_threading.py but it was added with 2.6 --- ./pypy-1.3/lib-python/2.5.2/test/test_threading.py ---------- status: unread -> chatting title: main thread not calling threading.shutdown() when exiting -> main thread not calling threading._shutdown() when exiting _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Thu Aug 19 16:19:15 2010 From: pypy-dev-issue at codespeak.net (Amaury Forgeot d Arc) Date: Thu, 19 Aug 2010 14:19:15 +0000 Subject: [PyPy-issue] [issue554] main thread not calling threading._shutdown() when exiting Message-ID: <1282227555.08.0.460293515295.issue554@> Amaury Forgeot d Arc added the comment: A tentative patch, which works at least on top of bin/py.py Where should the test be written? _______________________________________________________ PyPy development tracker _______________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: wait-for-threads.patch Type: application/octet-stream Size: 1956 bytes Desc: not available URL: From pypy-dev-issue at codespeak.net Tue Aug 24 12:07:44 2010 From: pypy-dev-issue at codespeak.net (paul clinch) Date: Tue, 24 Aug 2010 10:07:44 +0000 Subject: [PyPy-issue] [issue555] sys.exec_prefix Message-ID: <1282644464.15.0.851562296951.issue555@> New submission from paul clinch : The attribute exec_prefix is missing from sys. Its equivalent to os.path.dirname( sys.executable ). ---------- effort: easy messages: 1817 nosy: pclinch, pypy-issue priority: bug release: ??? status: unread title: sys.exec_prefix _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 12:15:13 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 24 Aug 2010 10:15:13 +0000 Subject: [PyPy-issue] [issue555] sys.exec_prefix Message-ID: <1282644913.66.0.326605754774.issue555@> Armin Rigo added the comment: I have sys.exec_prefix in my pypy-c. Which revision of pypy-c are you checking? ---------- status: unread -> chatting _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 12:15:41 2010 From: pypy-dev-issue at codespeak.net (paul clinch) Date: Tue, 24 Aug 2010 10:15:41 +0000 Subject: [PyPy-issue] [issue556] locking in msvcrt Message-ID: <1282644941.08.0.933170100375.issue556@> New submission from paul clinch : Added locking code to get Whoosh working on Windows, updated msvcrt.py from 1.3 attached. ---------- effort: easy files: msvcrt.py messages: 1819 nosy: pclinch, pypy-issue priority: feature release: ??? status: unread title: locking in msvcrt _______________________________________________________ PyPy development tracker _______________________________________________________ -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: msvcrt.py URL: From pypy-dev-issue at codespeak.net Tue Aug 24 16:28:02 2010 From: pypy-dev-issue at codespeak.net (Amaury Forgeot d Arc) Date: Tue, 24 Aug 2010 14:28:02 +0000 Subject: [PyPy-issue] [issue556] locking in msvcrt Message-ID: <1282660082.58.0.969525167351.issue556@> Amaury Forgeot d Arc added the comment: Thanks for the code! Merged with r76709. I changed it a bit to generate a correct IOError, and added tests. ---------- status: unread -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 16:49:00 2010 From: pypy-dev-issue at codespeak.net (paul clinch) Date: Tue, 24 Aug 2010 14:49:00 +0000 Subject: [PyPy-issue] [issue555] sys.exec_prefix Message-ID: <1282661340.01.0.965043307843.issue555@> paul clinch added the comment: Using 1.3 release. _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 16:50:13 2010 From: pypy-dev-issue at codespeak.net (paul clinch) Date: Tue, 24 Aug 2010 14:50:13 +0000 Subject: [PyPy-issue] [issue555] sys.exec_prefix Message-ID: <1282661413.17.0.472380097479.issue555@> paul clinch added the comment: Python 2.5.2 (75559, Jun 28 2010, 16:56:54) [PyPy 1.3.0] on win32 _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 16:51:57 2010 From: pypy-dev-issue at codespeak.net (Alex Gaynor) Date: Tue, 24 Aug 2010 14:51:57 +0000 Subject: [PyPy-issue] [issue555] sys.exec_prefix Message-ID: <1282661517.55.0.197377709408.issue555@> Alex Gaynor added the comment: exec_prefix was added by anto when he refactored a bunch of things, it's in trunk ATM and will be in the next release. ---------- status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 17:07:42 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 24 Aug 2010 15:07:42 +0000 Subject: [PyPy-issue] [issue554] main thread not calling threading._shutdown() when exiting Message-ID: <1282662462.15.0.659785371005.issue554@> Armin Rigo added the comment: Amaury: looks good to me. You could simplify a few lines by using space.finditem_str(w_modules, 'threading') instead of space.getitem(), which returns None instead of raising KeyError. _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 17:19:48 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 24 Aug 2010 15:19:48 +0000 Subject: [PyPy-issue] [issue543] pypy.lib._sre not tested and maybe not used? Message-ID: <1282663188.34.0.988482751677.issue543@> Armin Rigo added the comment: Killed the pure Python _sre.py in r76715. It was anyway based on the "old" algorithm, now gone. If people want a pure Python replacement for _sre, there is a rough one in pypy/rlib/rsre/rsre_re.py, used by tests only for now; we could expose it to lib_pypy/ if we wanted to. ---------- status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Tue Aug 24 17:36:34 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Tue, 24 Aug 2010 15:36:34 +0000 Subject: [PyPy-issue] [issue546] classes in translator.platform should use tuples in the class attributes Message-ID: <1282664194.45.0.228517161847.issue546@> Armin Rigo added the comment: Done in r76716, will be tested on various platforms this night. ---------- status: unread -> testing _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Wed Aug 25 15:43:59 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Wed, 25 Aug 2010 13:43:59 +0000 Subject: [PyPy-issue] [issue549] OS X build should not rely on libintl.h Message-ID: <1282743839.04.0.944016373209.issue549@> Armin Rigo added the comment: Fixed in r76726. ---------- status: unread -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Thu Aug 26 15:52:08 2010 From: pypy-dev-issue at codespeak.net (Armin Rigo) Date: Thu, 26 Aug 2010 13:52:08 +0000 Subject: [PyPy-issue] [issue557] reload(sys) mess Message-ID: <1282830728.18.0.562372667211.issue557@> New submission from Armin Rigo : reload(sys) is used by some programs to get sys.setdefaultencoding(). However on pypy it tends to have unwanted effects. For example we get "invalid file descriptor" on http://paste.pocoo.org/show/254667/ ---------- effort: ??? messages: 1828 nosy: pypy-issue priority: bug release: ??? status: unread title: reload(sys) mess _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Sat Aug 28 00:22:32 2010 From: pypy-dev-issue at codespeak.net (Florian Mayer) Date: Fri, 27 Aug 2010 22:22:32 +0000 Subject: [PyPy-issue] [issue558] Fatal RPython error: GAIError crashing interpreter Message-ID: <1282947752.68.0.173072038293.issue558@> New submission from Florian Mayer : I tried running my project's testsuite with pypy 1.3, and the interpreter crashed with the following error: http://bpaste.net/show/V8b8ypv9ReO1Gotdxu3s/ The code in question can be found at http://github.com/segfaulthunter/asynchia, the file run by the shell-script invoked in the paste is http://github.com/segfaulthunter/asynchia/blob/master/test/main.py. ---------- effort: ??? messages: 1829 nosy: pypy-issue, segfaulthunter priority: critical release: ??? status: unread title: Fatal RPython error: GAIError crashing interpreter _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Sat Aug 28 00:23:58 2010 From: pypy-dev-issue at codespeak.net (Florian Mayer) Date: Fri, 27 Aug 2010 22:23:58 +0000 Subject: [PyPy-issue] [issue558] Fatal RPython error: GAIError crashing interpreter Message-ID: <1282947838.45.0.727883830161.issue558@> Florian Mayer added the comment: The two links given in the note are the following (excluding the punctuation mark, that is): http://github.com/segfaulthunter/asynchia http://github.com/segfaulthunter/asynchia/blob/master/test/main.py Sorry for the inconvenience. ---------- status: unread -> chatting _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Sat Aug 28 01:32:28 2010 From: pypy-dev-issue at codespeak.net (Alex Gaynor) Date: Fri, 27 Aug 2010 23:32:28 +0000 Subject: [PyPy-issue] [issue234] Regular expression performance Message-ID: <1282951948.25.0.647316079876.issue234@> Alex Gaynor added the comment: Can this be closed now that armin has rewritten sre? _______________________________________________________ PyPy development tracker _______________________________________________________ From pypy-dev-issue at codespeak.net Sat Aug 28 19:01:15 2010 From: pypy-dev-issue at codespeak.net (Alex Gaynor) Date: Sat, 28 Aug 2010 17:01:15 +0000 Subject: [PyPy-issue] [issue558] Fatal RPython error: GAIError crashing interpreter Message-ID: <1283014875.13.0.340051534567.issue558@> Alex Gaynor added the comment: This should be fixed by r76770. ---------- status: chatting -> resolved _______________________________________________________ PyPy development tracker _______________________________________________________