[pypy-dev] Unbound method must be called with instance as first argument

Richard Emslie rxe at ukshells.co.uk
Tue Jul 6 15:12:04 CEST 2004


Hi Holger,

On Mon, 5 Jul 2004, holger krekel wrote:

>> The CPython implementation seems to be doing some hairy caching instead of
>> creating new method each __get__(), so it hard to tell if this is correct
>> behaviour.  And the above fixes are only based on my understanding of
>> desciptors, which has a high probability to be wrong.  If someone backs me
>> up I can commit fix 1. :-)
>
> I might have a lower probabiliy of beeing wrong but Samuele probably has one
> close to zero.  I suggest you go with your first solution (and also write
> some tests for it :-).

Thanks for feedback!  Done, even with some tests. ;-)

>
> Btw, it would be really nice to be able to run app-level tests against
> CPython apart from PyPy/std basically ensuring us we are beeing compatible.
> However, this probably can only be implemented nicely after we do the utest-switch.
>

Makes a lot of sense if we are in murky grounds with what the correct 
behaviour should be.  Looking forward to the new testing framework. :-)

Cheers,
Richard



More information about the Pypy-dev mailing list