[Python-Dev] Removing the GIL (Me, not you!) (original) (raw)
Jon Ribbens jon+python-dev at unequivocal.co.uk
Fri Sep 14 03:01:22 CEST 2007
- Previous message: [Python-Dev] Removing the GIL (Me, not you!)
- Next message: [Python-Dev] Removing the GIL (Me, not you!)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Sep 13, 2007 at 06:38:05PM -0500, skip at pobox.com wrote:
Hrvoje> More precisely, Python will call the deallocator appropriate for Hrvoje> the object type. If that deallocator does nothing, the object Hrvoje> continues to live. Such objects could also start out with a Hrvoje> refcount of sys.maxint or so to ensure that calls to the no-op Hrvoje> deallocator are unlikely.
Maybe sys.maxint/2? You'd hate for the first incref to invoke the deallocator even if it was a no-op.
I do believe I already suggested that ;-)
- Previous message: [Python-Dev] Removing the GIL (Me, not you!)
- Next message: [Python-Dev] Removing the GIL (Me, not you!)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]