python-ldap-dev — discussion among developers

Re: opening a connection with more than a single server

[Jens V. <je...@zo...>]

>> i had no idea that this ever worked, but apparently (i verified it with 
>> python-ldap 1.10alpha3) ldap.open used to accept a hostname string as 
>> argument with more than one LDAP host, separated by whitespace. this 
>> worked in a failover fashion where if one became unavailable the next 
>> one would be used to execute queries.
>
> 1. You have to decide what you want. You requested the old "parameter 
> signature" for ldap.open(). You remember? Think of defining the port 
> number...

this actually doesn't have anything to do with my earlier complaints about 
ldap.open. i'm just saying that apparently back in the 1.10 days ldap.open 
never checked the parameter and passed it straight to the ldap libraries, 
which would interpret it as "if the first server is dead just use the 
second".


> 2. I'd recommend you drop support for old python-ldap and use 
> ldap.initialize() directly. That's far more powerful anyway. Hmm, I would 
> have to remove/modify the is_ldap_url(uri) in the wrapper function for 
> handling the space separated list. But that's least of a problem.

my software is written so that it attempts to determine what version of 
python-ldap is in use and behave accordingly. anything that is not version 
2 and above uses ldap.open, 2.x uses ldap.initialize. simply dropping 
support for ldap.open is not an option, most everyone i know still uses 1.
10alpha3. but apart from that' that's not really my point. i'm just 
wondering if this "server fallback" behavior could find its way back into 
python-ldap2, regardless of connection building method used, because it 
seems it is supported by the OpenLDAP libraries and i am thinking it is a 
useful behavior. that's all.


> 3. IMHO it can't be used for fail-over. AFAIK simply the connection is 
> established to the first host reachable. You could argue that it works 
> kinda fail-over-like if you re-open the LDAP connection for the requests 
> all the time. But if you have a persistent connection you have to 
> implement fail-over by catching ldap.SERVER_DOWN. (I'm currently thinking 
> about sub-classing ldapobject.LDAPObject for this purpose. Note that 
> fail-over means repeating the whole connection-establishment sequence 
> after connecting to the replica).

it's true that the first available connection is used, and my software 
actually does re-open the connection every single time. so for this use 
case it does work like failover.

if i remember correctly i had at one time tried to come up with a way to 
test whether a given LDAP connection object was still good for use, but 
could not find anything that would not already involve making LDAP queries.
  so i assumed the difference in overhead was not that large. let me know 
if i am way off-base here, i could be talking out of my rear end. i have 
never experimented with long-lived connections. i am all for improving 
performance, if you can show me a good way to test existing connection 
objects and tell me that it is indeed faster to do it, i'm all ears.

jens

Re: opening a connection with more than a single server

[<mi...@st...>]

Jens Vagelpohl wrote:
> 
> i had no idea that this ever worked, but apparently (i verified it with 
> python-ldap 1.10alpha3) ldap.open used to accept a hostname string as 
> argument with more than one LDAP host, separated by whitespace. this 
> worked in a failover fashion where if one became unavailable the next 
> one would be used to execute queries.

1. You have to decide what you want. You requested the old 
"parameter signature" for ldap.open(). You remember? Think of 
defining the port number...

2. I'd recommend you drop support for old python-ldap and use 
ldap.initialize() directly. That's far more powerful anyway. Hmm, 
I would have to remove/modify the is_ldap_url(uri) in the wrapper 
function for handling the space separated list. But that's least 
of a problem.

3. IMHO it can't be used for fail-over. AFAIK simply the 
connection is established to the first host reachable. You could 
argue that it works kinda fail-over-like if you re-open the LDAP 
connection for the requests all the time. But if you have a 
persistent connection you have to implement fail-over by catching 
ldap.SERVER_DOWN. (I'm currently thinking about sub-classing 
ldapobject.LDAPObject for this purpose. Note that fail-over means 
repeating the whole connection-establishment sequence after 
connecting to the replica).

Ciao, Michael.

Re: problems ldap-module on AIX

[Jens V. <je...@zo...>]

the cycle-gc option should be safe again in python-2.1.3. it was rooted=20=

out after enough people complained about their Zope servers segfaulting,=20=

cycle-gc had a bug in it that was consequently fixed for 2.1.3

jens


On Tuesday, April 30, 2002, at 02:12 , Michael Str=F6der wrote:

> Jan Idzikowski wrote:
> >
> > i have a problem with the ldap-module on AIX.
>
> Disclaimer: I have no personal experience on AIX and
> IBM's C compiler.
>
> > I use Python-2.1.3 installed thread-safe with the IBM
> > C-Compiler cc_r and the option -qmaxmem=3D4000.
>
> I also have no clue what "Python-2.1.3 installed thread-safe" means.
>
> But please check the options you chose when compiling Python by =
issuing=20
> the following command in Python's source tree.
>
> $ ./configure --help
>
> Some candidates for further examination might be:
>
>   --without-gcc                   never use gcc
>   --with-signal-module            disable/enable signal module
>   --with(out)-threads[=3DDIRECTORY] disable/enable thread support
>   --with(out)-thread[=3DDIRECTORY]  deprecated; use
>                                   --with(out)-threads
>   --with-pth                      use GNU pth threading libraries
>   --with(out)-cycle-gc            disable/enable garbage collection
>   --with(out)-pymalloc            disable/enable specialized mallocs
>   --with-wctype-functions         use wctype.h functions
>   --with-dl-dld=3DDL_DIR,DLD_DIR    GNU dynamic linking
>   --with-fpectl                   enable SIGFPE catching
>
> At least on Linux I had to stay away of using cycle-gc and pymalloc.=20=

> (Check list archive!)
>
> Ciao, Michael.
>
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

opening a connection with more than a single server

[Jens V. <je...@zo...>]

hi everyone,

i had no idea that this ever worked, but apparently (i verified it with 
python-ldap 1.10alpha3) ldap.open used to accept a hostname string as 
argument with more than one LDAP host, separated by whitespace. this 
worked in a failover fashion where if one became unavailable the next one 
would be used to execute queries.

i am noticing that this no longer works on 2.0. is this (now that i know 
about it...) useful feature going to be available again at some point? 
(either in ldap.open or through ldap.initialize)

jens

Re: problems ldap-module on AIX

[<mi...@st...>]

Jan Idzikowski wrote:
 >
 > i have a problem with the ldap-module on AIX.

Disclaimer: I have no personal experience on AIX and
IBM's C compiler.

 > I use Python-2.1.3 installed thread-safe with the IBM
 > C-Compiler cc_r and the option -qmaxmem=4000.

I also have no clue what "Python-2.1.3 installed thread-safe" means.

But please check the options you chose when compiling Python by 
issuing the following command in Python's source tree.

$ ./configure --help

Some candidates for further examination might be:

   --without-gcc                   never use gcc
   --with-signal-module            disable/enable signal module
   --with(out)-threads[=DIRECTORY] disable/enable thread support
   --with(out)-thread[=DIRECTORY]  deprecated; use
                                   --with(out)-threads
   --with-pth                      use GNU pth threading libraries
   --with(out)-cycle-gc            disable/enable garbage collection
   --with(out)-pymalloc            disable/enable specialized mallocs
   --with-wctype-functions         use wctype.h functions
   --with-dl-dld=DL_DIR,DLD_DIR    GNU dynamic linking
   --with-fpectl                   enable SIGFPE catching

At least on Linux I had to stay away of using cycle-gc and 
pymalloc. (Check list archive!)

Ciao, Michael.

problems ldap-module on AIX

[Jan I. <idz...@at...>]

hallo,

i have a problem with the ldap-module on AIX.
I use Python-2.1.3 installed thread-safe with the IBM C-Compiler cc_r and the option -qmaxmem=4000.
With the normaly C-Compiler cc i could not start Zope and some other python application.
(but with the the normaly C-Compiler cc python install the ldap-module is working)
I have try to install the ldap-module with python setup.py build and get the warnings thet i have to compile it with the option MAXMEM > 2048. I have do this and the compile was fine. But i can't get the ldap-module working.
I import ldap and than i try l = ldap.initialize("ldap://my.ldapserver:389") and get a Segmentation fault (core dumped).

i think the problem is the thread-safe installation of python, and the ibm c-compiler, but i have to use this compiler and can't use a other, like gcc.

have anybody a idee?

thanks jan

idz...@at... 

Re: Installing source of python-ldap in suse...

[Jens V. <je...@zo...>]

josef,

first of all, i urge you to read more documentation in order to familiarize 
yourself better with basic concepts of LDAP, python and systems maintenance.

the warning you get means that the ldap module has been compiled with an 
*older* version of python than the python that runs your zope installation.
  that means you did not point the python-ldap configuration/compilation 
machinery to the correct python binary. even if it appears to be working 
correctly i would try and recompile the module with the correct python 
binary.

questions about the LDAPUserFolder are off-topic for this mailing list, 
which concerns itself with questions about the python-ldap module but not 
really with software that is built on top of python-ldap.

there is no concept like the LDAPUserFolder "catching" a user from the LDAP 
server. all users that can be found in the LDAP branch that you configured 
in the user folder with the users base/users search scope settings will be 
usable for authentication, provided the users also have some roles attached 
to them in the group entries that can be found in the LDAP branch you 
configured in the user folder using the groups base/groups search scope 
settings.

jens



On Saturday, April 27, 2002, at 01:48 , Josef Meile wrote:

> Finally I could do it. The LDAPUserFolder could be correctly imported
> into Zope. I just got the following warning:
>
> WARNING: Python C API version mismatch for module _ldap:
>   This Python has API version 1010, module _ldap has version 1007.
>
> But I could find some users on my LDAP server. Could this warning
> represent problems in the future?
>
> My last question:
> Will the LDAPUserFolder catch automatically every user from the
> LDAP server who try to log in? or do I have to seach and
> I add them by myself?
>
> Thanks for your patience,
> Josef.
>
>

Re: Installing source of python-ldap in suse...

[Josef M. <jm...@ho...>]

Finally I could do it. The LDAPUserFolder could be correctly imported
into Zope. I just got the following warning: 

WARNING: Python C API version mismatch for module _ldap:
  This Python has API version 1010, module _ldap has version 1007.

But I could find some users on my LDAP server. Could this warning
represent problems in the future?

My last question:
Will the LDAPUserFolder catch automatically every user from the
LDAP server who try to log in? or do I have to seach and
I add them by myself?

Thanks for your patience,
Josef.

Re: Installing source of python-ldap in suse...

[Josef M. <jm...@ho...>]

> um, then add the directory that contains python to your $PATH.
> you should be able to invoke python from anywhere then, and the scripts
> that you first referred to should now work.

I just did it but this error is still there:

make[1]: Entering directory
`/usr/local/python/2.1.3/python-ldap-1.10alpha3/Modules'
make[1]: *** No rule to make target
`/usr/local/lib/python2.1/config/Makefile', needed by `sedscript'.
Stop.
make[1]: Leaving directory
`/usr/local/python/2.1.3/python-ldap-1.10alpha3/Modules'
make: *** [boot] Error 2

It is looking for Makefile in /usr/local/lib/python2.1/config/, but that's
not the directory where
my python is installed.

This line is also wrong:
checking python version... 2.1

I have python 2.1.3 and not 2.1.

Re: Installing source of python-ldap in suse...

[Josef M. <jm...@ho...>]

>
> is python runnable from the command line? ie is it a problem with you
PATH?
>
Yes, but I have to go to the directory where it is.

Installing source of python-ldap in suse...

[Josef M. <jm...@ho...>]

Hi,
finally I decided to follow the advice of Jens and don't use
LDAPLoginAdapter and
LDAPUserManager. So, I just updated my Zope and python versions, and tried
to
install "python-ldap-1.10alpha3-182". I didn't choose
python-ldap-2.0.0pre04.tar.gz
because my Suse (version 7.3) doesn't come with the Openldap2 libraries.

The point is that I'm having the following message when trying to install
python-ldap
from source:

/bin/sh: python: command not found
/bin/sh: python: command not found
/bin/sh: python: command not found
make[1]: Entering directory
`/usr/local/python/2.1.3/python-ldap-1.10alpha3/Modu
les'
make[1]: *** No rule to make target `/lib/python/config/Makefile', needed by
`se
dscript'.  Stop.
make[1]: Leaving directory
`/usr/local/python/2.1.3/python-ldap-1.10alpha3/Modul
es'
make: *** [boot] Error 2

As I see, the problem is that the installation program doesn't find some
files of my python
compiler. The reason of this is that I had to install it from its source
tarball because my Suse
doesn't come with version 2.1.3. So, it creates everything under the same
directory; in my
case "/usr/local/python/2.1.3", and not in the two standard directories as
the usual installation
with "rpm" files.

How can I force the installation program to search the python compiler and
its libraries on its
current directory?

Thanks in advanced,
Josef.

Re: Ldap over SSL

[Jens V. <je...@zo...>]

if the LDAP server listens on a specific SSL-enabled port (meaning a =
port=20
that uses the ldaps protocol, the standard port for that being 636) then=20=

that is much easier to work with then StartTLS.

conn =3D ldap.initialize( 'ldaps://my.ldap.server' )
etc.

granted, this is not the "standard track", but it is very easy to use =
and=20
works reliably. i have once or twice tried to use StartTLS but all i =
ever=20
got were error messages that don't say anything about the actual error, =
and=20
my need to use StartTLS instead of ldaps was never great enough for me =
to=20
investigate further.

jens


On Friday, April 26, 2002, at 05:58 , Michael Str=F6der wrote:

> Sylvain Pereira wrote:
>>>> I am developping a python cgi application to administrate an ldap
>>>
>>> server for
>>>
>>>> a customer.
>>>
>>> What's the LDAP server product and OS?
>> Well it's iPlanet Directory Server 5.1 on SunOS 8, and I already =
checked=20
>> the SSL connection with a Java program (I am new to python).
>> The python cgi runs on an Irix 6.5
>
> If it's running on a Unix platform iDS 5.1 should also support =
StartTLS=20
> extended operation (not available with Win32 version) which is the=20
> standard track (see RFC2830).
>
>>>>> import ldap
>>>>> print ldap.__version__
>>>>
>> 2.0.0pre04
>>>>> ldap.set_option
>>>>
>> (ldap.OPT_X_TLS_CACERTFILE,'/usr/freeware/apache/conf/cert7.db')
>
> That's a Netscape certificate DB for Netscape's NSS lib. Something=20
> completely different.
>
> OpenLDAP2 uses OpenSSL as SSL lib. Therefore just use a "PEM file"=20
> containing the certificate. The same for the cert/key when using =
client=20
> certs for authentication.
>
> Ciao, Michael.
>

Re: Ldap over SSL

[<mi...@st...>]

Sylvain Pereira wrote:
> 
> I am developping a python cgi application to administrate an ldap server for
> a customer.

What's the LDAP server product and OS?

> so the ldap requests should be encrypted thanks to SSL.

See Demo/initialize.py for various examples using LDAP over SSL (LDAPS) or 
StartTLS extended operation (RFC2830).

Note that there are also options to set for validating the server's cert 
against a trusted root cert and doing client cert/key for strong authentication:

ldap.set_option(ldap.OPT_X_TLS_CACERTFILE,tls_cacert_full_pathname)

ldap.set_option(ldap.OPT_X_TLS_CERTFILE,tls_client_cert_full_pathname)
ldap.set_option(ldap.OPT_X_TLS_KEYFILE,tls_client_key_full_pathname)

Ciao, Michael.

Re: Ldap over SSL

[<mi...@st...>]

Sylvain Pereira wrote:
>>>I am developping a python cgi application to administrate an ldap
>>
>>server for
>>
>>>a customer.
>>
>>What's the LDAP server product and OS?
> 
> Well it's iPlanet Directory Server 5.1 on SunOS 8, and I already checked 
> the SSL connection with a Java program (I am new to python).
> The python cgi runs on an Irix 6.5

If it's running on a Unix platform iDS 5.1 should also support StartTLS 
extended operation (not available with Win32 version) which is the standard 
track (see RFC2830).

>>>>import ldap
>>>>print ldap.__version__
>>>
> 2.0.0pre04
> 
>>>>ldap.set_option
>>>
> (ldap.OPT_X_TLS_CACERTFILE,'/usr/freeware/apache/conf/cert7.db')

That's a Netscape certificate DB for Netscape's NSS lib. Something 
completely different.

OpenLDAP2 uses OpenSSL as SSL lib. Therefore just use a "PEM file" 
containing the certificate. The same for the cert/key when using client 
certs for authentication.

Ciao, Michael.

Re: Ldap over SSL

[Sylvain P. <spe...@so...>]

> > 
> > I am developping a python cgi application to administrate an ldap
> server for
> > a customer.
> 
> What's the LDAP server product and OS?
Well it's iPlanet Directory Server 5.1 on SunOS 8, and I already checked 
the SSL connection with a Java program (I am new to python).
The python cgi runs on an Irix 6.5

> See Demo/initialize.py for various examples using LDAP over SSL (LDAPS)
> or 
> StartTLS extended operation (RFC2830).
Thanks, I also took a look a the list archives ("TLS Context").

Still, I get the following error when testing with the python interpreter : 
############################################
>>> import ldap
>>> print ldap.__version__
2.0.0pre04
>>> ldap.set_option
(ldap.OPT_X_TLS_CACERTFILE,'/usr/freeware/apache/conf/cert7.db')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/freeware/lib/python2.1/site-packages/ldap/functions.py", line 101, 
in set_option
    _ldap_call(_ldap.set_option,option,invalue)
  File "/usr/freeware/lib/python2.1/site-packages/ldap/__init__.py", line 31, 
in _ldap_call
    result = apply(func,args,kwargs)
ldap.LDAPError: {'errnum': -1}
############################################

Any idea ?
___________________________________________________________

Sylvain Pereira
 06 18 65 32 59 (Mission - in a tall building far far away)
 01 41 26 62 61 (Siege - T-Systems e-technologies)
___________________________________________________________

Ldap over SSL

[Sylvain P. <spe...@so...>]

Hello,

I am developping a python cgi application to administrate an ldap server for
a customer. I can't use any of the existing products, they do not fit.

I can connect, add, modify, delete to the LDAP server. As I wrote it before,
it is an administration application, so the ldap requests should be encrypted
thanks to SSL.

I cannot find any documentation. My python is compiled with
openssl and ldap support.

Any idea ?

___________________________________________________________

Sylvain Pereira
 06 18 65 32 59 (Mission - in a tall building far far away)
 01 41 26 62 61 (Siege - T-Systems e-technologies)
___________________________________________________________

ldap module for windows

[Sharma, G. (NCI) <sha...@ma...>]

Hello All:

I need help in installation instructions for setting up python-ldap module
for windows. My application will be accessing ldap server from Zope 2.5.0
(binary version 2.1).

Thanks,
Gopesh 

docs of python-ldap in pdf formatted file

[Brian L. <se...@se...>]

Thanks all!

I downloaded and tried to print out pdf version of python-ldap
document but i couldn't it. I think page 6 is broken and 
my windows say can't print it. Can this be real? Others?

 - Brian,.

Re: trouble installing 2.0.0pre04

[<mi...@st...>]

Michael Schwartz wrote:
> 
> -L/usr/local/lib -llber -lldap -lresolv -o
> build/lib.freebsd-4.4-RELEASE-i386-2.1/_ldap.so
> /usr/libexec/elf/ld: cannot find -lresolv
> error: command 'cc' failed with exit status 1
 > [..]
> libs = lber ldap resolv

Should be on BSD:

libs = lber ldap

It works on your FreeBSD machine. Look into setup.cfg my home dir.

Ciao, Michael.

Re: trouble installing 2.0.0pre04

[<mi...@st...>]

Michael Str=F6der wrote:
> Michael Schwartz wrote:
>=20
>>
>> -L/usr/local/lib -llber -lldap -lresolv -o
>> build/lib.freebsd-4.4-RELEASE-i386-2.1/_ldap.so
>> /usr/libexec/elf/ld: cannot find -lresolv
>> error: command 'cc' failed with exit status 1
>=20
>  > [..]
>=20
>> libs =3D lber ldap resolv
>=20
>=20
> Should be on BSD:
>=20
> libs =3D lber ldap
>=20
> It works on your FreeBSD machine. Look into setup.cfg my home dir.

BTW: There's also a FreeBSD port for Python2.2 and
python-ldap (and even web2ldap).

Ciao, Michael.

trouble installing 2.0.0pre04

[Michael S. <mi...@id...>]

Hello,

I'm having trouble building python-ldap 2.0.0pre04... any hints /
suggestions would be greatly appeciated!

tia,

Mike Schwartz
mi...@id...

========================= output ===============================

# python setup.py build
running build
running build_py
warning: build_py: file Lib/ldap.py (for module ldap) not found
not copying Lib/ldap/__init__.py (output up-to-date)
not copying Lib/ldap/async.py (output up-to-date)
not copying Lib/ldap/functions.py (output up-to-date)
not copying Lib/ldap/ldapobject.py (output up-to-date)
not copying Lib/ldap/modlist.py (output up-to-date)
not copying Lib/ldapurl.py (output up-to-date)
not copying Lib/ldif.py (output up-to-date)
warning: build_py: file Lib/ldap.py (for module ldap) not found
running build_ext
building '_ldap' extension
skipping Modules/LDAPObject.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/LDAPObject.o up-to-date)
skipping Modules/common.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/common.o up-to-date)
skipping Modules/constants.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/constants.o up-to-date)
skipping Modules/errors.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/errors.o up-to-date)
skipping Modules/functions.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/functions.o up-to-date)
skipping Modules/ldapmodule.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/ldapmodule.o up-to-date)
skipping Modules/linkedlist.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/linkedlist.o up-to-date)
skipping Modules/message.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/message.o up-to-date)
skipping Modules/template.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/template.o up-to-date)
skipping Modules/version.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/version.o up-to-date)
skipping Modules/options.c
(build/temp.freebsd-4.4-RELEASE-i386-2.1/options.o up-to-date)
cc -shared -pthread build/temp.freebsd-4.4-RELEASE-i386-2.1/LDAPObject.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/common.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/constants.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/errors.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/functions.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/ldapmodule.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/linkedlist.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/message.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/template.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/version.o
build/temp.freebsd-4.4-RELEASE-i386-2.1/options.o -L/usr/lib
-L/usr/local/lib -llber -lldap -lresolv -o
build/lib.freebsd-4.4-RELEASE-i386-2.1/_ldap.so
/usr/libexec/elf/ld: cannot find -lresolv
error: command 'cc' failed with exit status 1


========================= setup.cfg =========================

# Section for compiling the C extension module
# for wrapping OpenLDAP 2 libs

[_ldap]
class = OpenLDAP2
library_dirs = /usr/lib /usr/local/lib
include_dirs = /usr/include /usr/local/include
libs = lber ldap resolv

# Installation options

[install]

compile = 1
optimize = 1

=============================================================

Re: Schema support

[<mi...@st...>]

Joe Little wrote:
> Now that some of this has been commited, any interest in making another -pre
> release?

Far too early to ask for a pre-release.

Ciao, Michael.

Re: Schema support

[Joe L. <jl...@op...>]

Now that some of this has been commited, any interest in making another -pr=
e
release?

On 4/15/02 10:59 PM, "Michael Str=F6der" <mi...@st...> wrote:

> Hans Aschauer wrote:
>> I have finished a first version of schema support for python-ldap.
>=20
> I tried your attachments. But to me it seems that there is lacking
> something. The build went fine but the functions do not appear in extensi=
on
> module _ldap.
>=20
> Maybe you also modified functions.c?
>=20
> Please re-send most recent version of your schema support and SASL patche=
s.
>=20
> Ciao, Michael.
>=20
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: Error message when running python-ldap under Zope and Suse

[<mi...@st...>]

Josef Meile wrote:
> You mean if there is a file called python and nothing else in the folder
> Zope2.x.x/bin?
> If so, then I have a binary version, so I'll have to install the source. By
> the way, where should I compile the source? I guess I've to install the
> version 1.5.2 as well.

You should probably try to install all the packages from the SuSE Linux. 
Don't start mixing without really knowing what to do!

AFAIK SuSE 7.3 comes with Python 2.1, (outdated) python-ldap 1.10alpha3 and 
Zope.

Ciao, Michael.

Re: Error message when running python-ldap under Zope and Suse

[<mi...@st...>]

Jens Vagelpohl wrote:
> i assume the problem is trying to mix things that cannot be mixed using 
> the packages provided by suse.

Yes.

> from what i can deduct sude comes with python2.1 and if python-ldap is a 
> suse package i assume it is compiled for this specific python2.1. however,
>  the zope he has only runs on 1.5.2. so he cannot achieve the desired 
> goal using only prepackaged stuff.

Yes.

But SuSE also ships with Zope (not sure which version).
I guess it works with the Python 2.1 SuSE RPM package.

Ciao, Michael.