why didn't it work?
michael at stroeder.com
Tue Jan 29 09:21:16 CET 2002
Jens Vagelpohl wrote:
> actually it does not work well in the latest python-ldap. importing _ldap
> will not raise an ImportError. but _ldap is crippled and will blow up the
> first time you try to call something with it.
> everywhere i go on the python-ldap.sourceforge.net site the docs talk of
> the "_ldap" module and code examples use "import _ldap".
The former code examples were obviously wrong. The code examples
I've checked during the last months definitely did not import _ldap.
> that's probably
> why i assumed that that's the canonical way of doing things.
> i'm just wondering why in the world that's deprecated now and importing
> ldap is the only way it works.
Now I'm wondering why you folks on this list didn't respond to my
messages weeks ago. The changes were announced and I asked for
feedback. Check the archives.
Note that there are significant changes going on. The Win32 binaries
floating around are python-ldap version 1.x linked against ancient
Umich libs whereas CVS version is linked against OpenLDAP 2 libs.
I'm trying to preserve backwards compability but you have to
definitely fix your code to import ldap not _ldap.
More information about the python-ldap