> I'm lost there. Isn't CPython using reference counting (i.e updating the
> object's state at each reference creation/deletion, and deleting the
> objects as soon as they have no more references to them) ? It seemed to
> me that generational GC only applied to periodic GCs, like tracing
> garbage
Martin v. Löwis a écrit :
Is there any interest in generational garbage collection in Python these days ?
Anyone working on it ?
This is the time machine at work: the garbage collector in CPython *is*
generational (with three generations).
Regards,
Martin
--
http://mail.python.org/mailma
> Is there any interest in generational garbage collection in Python these days
> ?
>
> Anyone working on it ?
This is the time machine at work: the garbage collector in CPython *is*
generational (with three generations).
Regards,
Martin
--
http://mail.python.org/mailman/listinfo/python-list
Borked Pseudo Mailed pseudo.borked.net>
writes:
>
> Hello,
>
> Is there any interest in generational garbage
> collection
> in Python these days ?
>
> Anyone working on it ?
The PyPy project has implemented more GC's than you want to
think about
including a ref counting gc, mark-sweep, and
se
Borked Pseudo Mailed wrote:
Hello,
Is there any interest in generational garbage collection in Python these days ?
Anyone working on it ?
Thanks
Not really all that useful for CPython (you cannot move live objects,
without breaking faith with C-coded extensions). PyPy would be where
to look
Hello,
Is there any interest in generational garbage collection in Python these days ?
Anyone working on it ?
Thanks
--
http://mail.python.org/mailman/listinfo/python-list
