From: David L. <dav...@cs...> - 2001-05-12 12:05:43
|
fellas, I have committed two files (setup.py and setup.cfg) into CVS. this is because I want to use Python's distutils package for distributing future python-ldap modules. distutils should make it easier to build binary distributions that do the right thing when installing. much less hassle to build releases. (people who add new stuff to CVS may also have to edit setup.py now!) So, to build python-ldap in the new way, simply type python setup.py build You may need to edit setup.cfg first. Full documentation for distutils is on the python web site. fortunately, (or unfortunately depending on how you look at it) there is no support in distutils for autodetecting features about the ldap library. i plan to * move towards just supporting OpenLDAP 2, and * delete all the gnu autoconf gunk If someone wants to support mozilla's or solaris' library etc they should speak up now and be willing to help add support. (email me now!) for this contingency, I have created rough, manual descriptions of what #defines etc to enable when OpenLDAP2 is selected. By default, openldap is selected in setup.cfg, which is a file that looks like this: [_ldap] class = OpenLDAP2 perhaps in the future, python programs will be able to check what library is being used by doing something with it; e.g.: if _ldap.libclass == "OpenLDAP2": do_something_openldap_specific() your comments? d -- David Leonard Dav...@cs... Dept of Comp. Sci. and Elec. Engg _ Room:78-640 Ph:+61 7 336 51187 The University of Queensland |+| http://www.csee.uq.edu.au/~leonard/ QLD 4072 AUSTRALIA ~` '~ B73CD65FBEF4C089B79A8EBADF1A932F13EA0FC8 Why are apartments so close together? |
From: Michael <mi...@st...> - 2001-05-12 12:40:34
|
David Leonard wrote: > > i plan to > * move towards just supporting OpenLDAP 2, and > * delete all the gnu autoconf gunk How about thread-safety only possible with Mozilla SDK? Hmm, I thought of the following: SWIG modules for every LDAP C SDK out there which should not be directly used by an application. The SWIG modules should wrap *all* functions provided by a C SDK. Python LDAPObject class as an abstraction layer which hides the SWIG-ed functions of the C SDK providing an API compatible to recent python-ldap. For each underlying C SDK there should be a specific implementation class. Now the SWIG folks could start wrapping the OpenLDAP 1.2.x, 2.0.x and Mozilla C SDK without having to provide a nice Python API and I promise to write Python wrapper classes compatible to recent python-ldap. This is just an quick idea. Let me know what you all think. Ciao, Michael. |
From: Joe L. <jl...@op...> - 2001-05-12 20:44:28
|
I've been conversing with sasha at free.de, who has a rough cut python-ldap swig module done. He has had it work against Netscape, OpenLDAP, etc. to various extents (you can build out separate modules for each SDK). Maybe we can finish that work and thus allow for what you ask.. Especially if you are willing to finish off the python-ldap api stuff :) On Sat, 12 May 2001, Michael Str=F6der wrote: > David Leonard wrote: > > > > i plan to > > * move towards just supporting OpenLDAP 2, and > > * delete all the gnu autoconf gunk > > How about thread-safety only possible with Mozilla SDK? > > Hmm, I thought of the following: > > SWIG modules for every LDAP C SDK out there which should not be > directly used by an application. The SWIG modules should wrap *all* > functions provided by a C SDK. > > Python LDAPObject class as an abstraction layer which hides the > SWIG-ed functions of the C SDK providing an API compatible to recent > python-ldap. For each underlying C SDK there should be a specific > implementation class. > > Now the SWIG folks could start wrapping the OpenLDAP 1.2.x, 2.0.x > and Mozilla C SDK without having to provide a nice Python API and I > promise to write Python wrapper classes compatible to recent > python-ldap. > > This is just an quick idea. Let me know what you all think. > > Ciao, Michael. > > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > http://lists.sourceforge.net/lists/listinfo/python-ldap-dev > |
From: Michael <mi...@st...> - 2001-05-12 21:22:11
|
Joe Little wrote: > > I've been conversing with sasha at free.de, who has a rough cut > python-ldap swig module done. He has had it work against Netscape, > OpenLDAP, Sascha, please give us a status report which vendors/versions of LDAP C SDKs you wrapped with your SWIG approach and which functionality it has. Ciao, Michael. |
From: Sascha G. <sas...@op...> - 2001-05-13 07:59:35
|
On Sat, 12 May 2001 23:11:55 +0200 Michael Ströder <mi...@st...> wrote: > Joe Little wrote: > > > > I've been conversing with sasha at free.de, who has a rough cut > > python-ldap swig module done. He has had it work against Netscape, > > OpenLDAP, > Just openldap1.x. I have send a plan to jl...@op..., how swig-ldap-0.2 *could* look like. This plan didn't have much text going with it - I just thought its clear it couldnt match current swig-ldap, since no interface for netscape, sun or whatever is included. Sorry for not communicating clear enough. > Sascha, > > please give us a status report which vendors/versions of LDAP C SDKs > you wrapped with your SWIG approach and which functionality it has. > Nothing compared to python-ldap. Some basic stuff to handle some simple adding, searching and deletion of records. -- /* Yeah */ |