|
From: Jens V. <je...@zo...> - 2002-01-28 15:57:48
|
i'm very surprised. i was under the impression that it was just the = other=20 way around: importing _ldap was the canonical way and importing ldap = only=20 existed for backwards compatibility. i'm confused. jens On Monday, January 28, 2002, at 10:29 , Michael Str=F6der wrote: > Jens Vagelpohl wrote: >> >> i'm getting complaints about this from people who use some of my = products >> that rely on python-ldap. one guy uses a CVS checkout from january = 4th.=20 >> is >> the CVS version hosed? > > Don't import _ldap. Despite some code examples this was never good > practice. > >> if I try to call the "_ldap.open" function, it fails : >> module _ldap does not have such function. > > Yes. > >>>>> can you import "ldap"? >> Yes, I can, and I can call functions "ldap.open", "ldap.bind_s", etc. >> ******* > > There's no reason to import _ldap. Don't do that. Everything's > wrapped correctly in module ldap.ldapobject. > > Ciao, Michael. |