Re: [pypy-dev] Unable to translate locks
Hi, well, I've solved this problem. The point is that the lock in my example is created at import time, before translation. Works fine if the initialization is moved into a function that can be translated. Marek Paška On Wed, Jul 30, 2008 at 18:10, Marek Paška <paskma@gmail.com> wrote:
Hi!
I tried this option and it does not change anything. In fact, this option is not even needed for pypy interpreter translation, with --withmod-thread the pypy interpreter is compiled successfully and the thread module is usable regardless of the --thread option. As I understand, the --thread option only affects runtime behavior, e.g., ensures that GC is aware of multiple threads or so. Or am I wrong?
It seems, there is some magic used when the thread module is translated. Something that affects annotation... I don't know. I spent several days debugging it but PyPy is rather complex.
Cheers,
Marek Paška
On Wed, Jul 30, 2008 at 09:34, Armin Rigo <arigo@tunes.org> wrote:
Hi,
On Tue, Jul 29, 2008 at 12:55:33PM +0200, Marek Pa?ka wrote:
paskma@paskma:goal$ ./translate.py mytasks_err.py
I think you need to specify the --thread option:
./translate.py --thread mytasks_err.py
A bientot,
Armin
participants (1)
-
Marek Paška