Why LDAPObject.._ldap_object_lock around library calls?
key-ldap-dev at KSquared.NET
Wed May 5 03:10:33 CEST 2004
I'm having a little trouble with the _ldap_object_lock in the
LDAPObject around ldap library function calls. Is the link
to protect against threads making function calls when the _ldap
module is linked against the non-reentrant version of the libldap?
That is, wouldn't it be safe to get rid of the _ldap_object_lock
references in LDAPObject._ldap_call() if the module is linked
against libldap_r? Or is there some other, non-threadsafe reason
that I'm missing?
Thanks for any info,
More information about the python-ldap