[pypy-dev] thunk object space : become() quirks
Carl Friedrich Bolz
cfbolz at gmx.de
Thu Dec 6 22:12:50 CET 2007
Carl Friedrich Bolz wrote:
> Boris Borcic wrote:
>> Looking for a way to use pypy in any manner, I came up with an idea for a
>> deterministic sudoku solver that would use the 'become()' feature of the thunk
>> object space. However, this doesn't work as I expected. The following shell
>> trace illustrates my problem. Is this a bug or otherwise ? Can anybody explain ?
>> BTW, I am using the pypy 1.0.0 build 41438 windows binary distribution.
>> [subquestion : is pypy-dev appropriate for such a question ?]
> It's a bug, I have a clue where it is and will try to fix it. Thanks for
> reporting! Yes, the list is completely appropriate.
Some updates on this thing: We discussed the problem extensively on the
sprint and the think is that this shows a serious problem with the way
the thunk object space is done. We have no concrete clue how to solve it
yet. Thunks themselves are also affected by this bug, but only in more
I created an issue in the bug tracker for this:
Thanks again for reporting this – it only shows again that we should
actually implement real stuff with thunks to get the bugs out of it.
More information about the Pypy-dev