Hi!
My world just turned upside down. I've been using asynchronous
python-ldap with code that looks something like this, for a long time:
import ldap
ldapconn = ldap.initialize(uri)
searchsid = ldapconn.search(base, scope, filter, attrlist)
while 1:
(code, data) = ldapconn.result(msgid=searchsid, all=0)
if ldap.RES_SEARCH_RESULT == code:
break
This has worked very well. Until today, on a Novell Linux Desktop 9,
with a python-ldap package borrowed from SLES9, with rpm package
version python-ldap-2.0.0pre19-75.1.
In that package, ldap.RES_SEARCH_RESULT was 'RES_SEARCH_RESULT' and
code was 101.
In all other python-ldap packages I've seen, the
ldap.RES_SEARCH_RESULT has always been a number (101). The code
returned from ldapconn.result has also always been a number. Both are
numbers in my Debian-packaged python2.3-ldap 2.0.4-1.
Am I confused? Has there been an API change that I've missed? Is the
SuSE package terribly wrong? (could be a problem caused by the running
of a SLES9 package on top of NLD9, but still very odd)
Regards,
\EF
--
Erik Forsberg OpenSource-based Thin Client Technology
Cendio AB Phone: +46-13-21 46 00
Web: http://www.thinlinc.com
|
