Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-08 Thread Christian Tismer
On 2/8/11 9:25 PM, Philip Jenvey wrote: > On Feb 5, 2011, at 9:04 PM, Dino Viehland wrote: > >> Christianwrote: >>> Howdy, >>> >>> studying the differences of PyPy vs. CPython, most seem to be fine; one >>> thing where I an unsure is the __del__ behavior. >>> >>> I am not addressing its delayed cal

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-06 Thread Armin Rigo
Hi Alex, On Sun, Feb 6, 2011 at 6:26 AM, Alex Gaynor wrote: >> Then you can change __del_ to whatever you want later. > > I think it'll work with pypy, *and* still trigger the warning, but that's > from memory. Just try it out then :-) The answer is no. You get a warning only if a '__del__' en

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Alex Gaynor
On Sun, Feb 6, 2011 at 12:04 AM, Dino Viehland wrote: > > Christianwrote: > > Howdy, > > > > studying the differences of PyPy vs. CPython, most seem to be fine; one > > thing where I an unsure is the __del__ behavior. > > > > I am not addressing its delayed call or the number it is called, this i

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Dino Viehland
Christianwrote: > Howdy, > > studying the differences of PyPy vs. CPython, most seem to be fine; one > thing where I an unsure is the __del__ behavior. > > I am not addressing its delayed call or the number it is called, this is > similar to > Jython and IronPython. > > But assigning to __del_

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Carl Friedrich Bolz
On Saturday, February 5, 2011, Christian Tismer wrote: > Ah, we do get a warning, that is good, did not know. > > Anyway, the concept of RPython is pretty old, since we needed > something that is treatable. And RPython is a good compromise > for most things. > > Meanwhile, a lot of evolution has

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Christian Tismer
On 2/6/11 12:25 AM, Benjamin Peterson wrote: > 2011/2/5 Christian Tismer: >> On 2/5/11 11:47 PM, Benjamin Peterson wrote: >>> 2011/2/5 Christian Tismer: Howdy, studying the differences of PyPy vs. CPython, most seem to be fine; one thing where I an unsure is the __del__ behavior

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Benjamin Peterson
2011/2/5 Christian Tismer : > On 2/5/11 11:47 PM, Benjamin Peterson wrote: >> >> 2011/2/5 Christian Tismer: >>> >>> Howdy, >>> >>> studying the differences of PyPy vs. CPython, most seem to be fine; >>> one thing where I an unsure is the __del__ behavior. >>> >>> I am not addressing its delayed cal

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Christian Tismer
On 2/5/11 11:47 PM, Benjamin Peterson wrote: > 2011/2/5 Christian Tismer: >> Howdy, >> >> studying the differences of PyPy vs. CPython, most seem to be fine; >> one thing where I an unsure is the __del__ behavior. >> >> I am not addressing its delayed call or the number it is called, this >> is sim

Re: [pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Benjamin Peterson
2011/2/5 Christian Tismer : > Howdy, > > studying the differences of PyPy vs. CPython, most seem to be fine; > one thing where I an unsure is the __del__ behavior. > > I am not addressing its delayed call or the number it is called, this > is similar to Jython and IronPython. > > But assigning to _

[pypy-dev] Compat. in 1.4.1 __del__

2011-02-05 Thread Christian Tismer
Howdy, studying the differences of PyPy vs. CPython, most seem to be fine; one thing where I an unsure is the __del__ behavior. I am not addressing its delayed call or the number it is called, this is similar to Jython and IronPython. But assigning to __del__ after a class is created, is that so