patch to compile with OpenLDAP 2.0.7
michael at stroeder.com
Fri Nov 17 19:51:10 CET 2000
Konstantin Chuguev wrote:
> Knowing which features are supported is useful though. But it doesn't
> necessarily have to be done by creating constants in python-ldap which values
> are set at the compilation time. For example, if you try to set the version
> attribute to any value in python-ldap compiled against OpenLDAPv1.2, you'll get
> an exception; same case with using ufn_ methods etc.
Yes, an exception is sufficient.
Well, let me repeat my position: You can change python-ldap to be
completely incompatible to previous versions. I'm fine with that if
I get full LDAPv3 support (some steps already made by Konstantin
:-), VLV, SSL/TLS, bla di bla...
> I didn't touch anything related to Netscape/Mozilla/Umich SDK in my
Drop it. Since OpenLDAP 2.0.x is out and seems to be reasonable
stable there's no good reason anymore to support outdated APIs. (In
the case of Netscape and Novell you even can't download them
> Maybe we should consider extending LDAPerror function somehow...
Anyway, drop compability whereever it's necessary to have a cleaner
design! I'm fine with a new CVS branch for python-ldap.
For compability with old python-ldap we can write a Python wrapper
More information about the python-ldap