Re: [Python-Dev] Marking GC details as CPython-only

2013-02-14 Thread Antoine Pitrou
Le Wed, 13 Feb 2013 20:50:51 +, Richard Oudkerk a écrit : > On 13/02/2013 7:25pm, Antoine Pitrou wrote: > > I think resurrecting objects from __del__ is crazy, so IMO what you > > suggest is fine. > > You mean like subprocess.Popen.__del__? I quite agree. Ouch. I didn't know about that. Re

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Richard Oudkerk
On 13/02/2013 7:25pm, Antoine Pitrou wrote: I think resurrecting objects from __del__ is crazy, so IMO what you suggest is fine. You mean like subprocess.Popen.__del__? I quite agree. -- Richard ___ Python-Dev mailing list Python-Dev@python.org htt

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Barry Warsaw
On Feb 13, 2013, at 08:30 PM, Armin Rigo wrote: >Actually right now, at the exit of the interpreter, we just leave the >program without caring about running any __del__. This might mean >that in a short-running script no __del__ is ever run. I'd add this >question to your original list: is it go

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Maciej Fijalkowski
On Wed, Feb 13, 2013 at 9:40 PM, Antoine Pitrou wrote: > On Wed, 13 Feb 2013 20:30:18 +0100 > Armin Rigo wrote: >> Hi, >> >> On Wed, Feb 13, 2013 at 8:22 PM, Maciej Fijalkowski wrote: >> > I think it's well documented you should not rely on stuff like that >> > being run at the exit of the inter

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Antoine Pitrou
On Wed, 13 Feb 2013 20:30:18 +0100 Armin Rigo wrote: > Hi, > > On Wed, Feb 13, 2013 at 8:22 PM, Maciej Fijalkowski wrote: > > I think it's well documented you should not rely on stuff like that > > being run at the exit of the interpreter. > > Actually right now, at the exit of the interpreter,

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Armin Rigo
Hi, On Wed, Feb 13, 2013 at 8:22 PM, Maciej Fijalkowski wrote: > I think it's well documented you should not rely on stuff like that > being run at the exit of the interpreter. Actually right now, at the exit of the interpreter, we just leave the program without caring about running any __del__.

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Antoine Pitrou
On Wed, 13 Feb 2013 20:48:08 +0200 Maciej Fijalkowski wrote: > > Things were pypy differs: > > * finalizers in pypy will be called only once, even if the object is > resurrected. I'm not sure if this is detail or we're just plain > incompatible. I think this should be a detail. > * pypy breaks

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Maciej Fijalkowski
On Wed, Feb 13, 2013 at 9:09 PM, Xavier Morel wrote: > On 2013-02-13, at 19:48 , Maciej Fijalkowski wrote: > >> Hi >> >> I've tried (and failed) to find what GC details (especially finalizer >> semantics) are CPython only and which ones are not. The best I could >> find was the documentation of __

Re: [Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Xavier Morel
On 2013-02-13, at 19:48 , Maciej Fijalkowski wrote: > Hi > > I've tried (and failed) to find what GC details (especially finalizer > semantics) are CPython only and which ones are not. The best I could > find was the documentation of __del__ here: > http://docs.python.org/2/reference/datamodel.ht

[Python-Dev] Marking GC details as CPython-only

2013-02-13 Thread Maciej Fijalkowski
Hi I've tried (and failed) to find what GC details (especially finalizer semantics) are CPython only and which ones are not. The best I could find was the documentation of __del__ here: http://docs.python.org/2/reference/datamodel.html Things were pypy differs: * finalizers in pypy will be calle