[Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail (original) (raw)
Tim Peters tim.one@comcast.net
Wed, 05 Feb 2003 13:16:02 -0500
- Previous message: [Python-Dev] I have something I'd like to use the farm for.
- Next message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Christian Tismer]
It might be not so hard to make trashcan able to register new types at run-time.
They don't have to do anything extra now -- registering with gc is sufficient in current CVS. It's also a fine fit: if they're fat containers for which the trashcan is appropriate, they can also be involved in cycles.
Note too that people can get back more memory than gc consumes by declaring new-style classes to use slots. That's a new memory-optimization gimmick, and an effective one.
- Previous message: [Python-Dev] I have something I'd like to use the farm for.
- Next message: [Python-Dev] Python 2.3a1's mandatory use of cyclic GC causes existing applications to fail
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]