This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author larry
Recipients larry, vstinner
Date 2016-04-14.07:55:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1460620546.75.0.247903713074.issue26753@psf.upfronthosting.co.za>
In-reply-to
Content
Obmalloc now has theoretical support for locking.  I say theoretical because I'm not convinced it's ever been used.

The interface is defined through five macros:
    SIMPLELOCK_DECL
    SIMPLELOCK_INIT
    SIMPLELOCK_FINI
    SIMPLELOCK_LOCK
    SIMPLELOCK_UNLOCK

Internally these are used to define an actual lock to be used in the module.  The lock, "_malloc_lock", is declared, then four defines are made building on top of the SIMPLELOCK macros, named:
    LOCK
    UNLOCK
    LOCK_INIT
    LOCK_FINI

LOCK_INIT and LOCK_FINI are never called.  So unless your lock doesn't happen to require initialization or shutdown, this API is misimplemented.

Victor: this was your work, right?  If not, sorry, please unassign/de-nosy yourself.
History
Date User Action Args
2016-04-14 07:55:46larrysetrecipients: + larry, vstinner
2016-04-14 07:55:46larrysetmessageid: <1460620546.75.0.247903713074.issue26753@psf.upfronthosting.co.za>
2016-04-14 07:55:46larrylinkissue26753 messages
2016-04-14 07:55:46larrycreate