python-ldap-dev — discussion among developers

Re: incompatibility with pypgsql?

[Allan S. <as...@in...>]

On Mon, 10 Feb 2003, [ISO-8859-1] Michael Str=F6der wrote:

> Allan Streib wrote:
> > Wondering if anyone has noted the following problem:
> >
> > import ldap
> > from pyPgSQL import libpq
> > [..]
> > c =3D libpq.PQconnectdb(host, dbname, user, password)
> > Segmentation fault.
> >
> > This is with pypgsql 2.2 and python-ldap-2.0.0-pre06.
>
> Note sure if that helps but please check an old message appended below.

Just thought I'd let everyone know that the segmentation fault described
above does not occur if I build python-ldap using the openldap 2.0.27
libs.  I still don't understand why this is causing a segfault in pypgsql
but perhaps something in the openldap 2.0.23 libs is overwriting something
that happens to be in pypgsql's space, and this problem has been fixed in
the 2.0.27 openldap libs.

Allan

trouble with ldap_r

[Allan S. <as...@in...>]

Trying to build -pre06, with the following in setup.cfg:

libs = ldap_r lber sasl ssl crypto

Once built, I try to test it by firing up python (working dir
build/lib.linux-i686-2.2/) and importing ldap.  My session looks like:

Python 2.2.1 (#1, May 14 2002, 16:46:46)
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-98)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ldap
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "ldap/__init__.py", line 21, in ?
    from _ldap import *
ImportError: /usr/kerberos/lib/libk5crypto.so.3: shared object not open

I saw this previously and thought it might be that I was using
openldap-2.0.23, contrary to advice in the README file.  So I built 2.0.27
and used those libraries to build python-ldap-2.0.0-pre06

Looking at ldd output for _ldap.so, it seems to be finding
everything:

$ ldd _ldap.so
        libldap_r.so.2 => /home/astreib/seg/openldap-2.0.27/libraries/libldap_r/.libs/libldap_r.so.2 (0x4000f000)
        liblber.so.2 => /home/astreib/seg/openldap-2.0.27/libraries/liblber/.libs/liblber.so.2 (0x40040000)
        libsasl.so.7 => /usr/local/lib/libsasl.so.7 (0x4004b000)
        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4005e000)
        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4008b000)
        libc.so.6 => /lib/libc.so.6 (0x40142000)
        libkrb4.so.2 => /usr/kerberos/lib/libkrb4.so.2 (0x40278000)
        libdes425.so.3 => /usr/kerberos/lib/libdes425.so.3 (0x4028c000)
        libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x40290000)
        libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x402e9000)
        libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x402fa000)
        libdb-4.0.so => /usr/local/BerkeleyDB.4.0/lib/libdb-4.0.so (0x402fd000)
        libdl.so.2 => /lib/libdl.so.2 (0x40389000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x4038d000)
        libpam.so.0 => /lib/libpam.so.0 (0x403ba000)
        libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2 (0x403c3000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x403d6000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

Can anyone shed any light on what exactly the error "shared object not
open" means?

If I specify ldap instead of ldap_r in my setup.cfg libs, I do not get
this error on import ldap.

Allan

Re: incompatibility with pypgsql?

[Allan S. <as...@in...>]

On Monday, February 10, 2003, at 10:58 AM, Michael Str=F6der wrote:

> Watch out for _ldap.so (pre06) and _ldapmodule.so (pre04). You have to=20=

> remove _ldapmodule.so.

find(1) reveals only _ldap.so

# find / -name _ldap\*.so
/usr/local/lib/python2.2/site-packages/_ldap.so
/usr/local/src/python-ldap-2.0.0pre06/build/lib.linux-i686-2.2/_ldap.so
/usr/local/src/python-ldap-2.0.0pre04/build/lib.linux-i686-2.2/_ldap.so

(Currently I have the -pre04 installed)

Allan

Re: incompatibility with pypgsql?

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

Allan Streib wrote:
> Wondering if anyone has noted the following problem:
>=20
> import ldap
> from pyPgSQL import libpq
> [..]
> c =3D libpq.PQconnectdb(host, dbname, user, password)
> Segmentation fault.
>=20
> This is with pypgsql 2.2 and python-ldap-2.0.0-pre06.=20

Note sure if that helps but please check an old message appended below.

 > The problem does not occur with python-ldap-2.0.0-pre04.

Are you sure that there's not library mix of 2.0.0pre04 and pre06?
Watch out for _ldap.so (pre06) and _ldapmodule.so (pre04). You have to=20
remove _ldapmodule.so.

Check if you have

Ciao, Michael.

-------- Original Message --------
Subject: python-ldap and --with-pymalloc
Date: Sun, 18 Nov 2001 17:09:17 +0100
From: Michael Str=F6der <mi...@st...>
Reply-To: mi...@st...
Organization: stroeder.com
To: python-ldap-dev <pyt...@li...>

HI!

It seems that I found the solution why python-ldap was seg faulting
with my Python 2.1 installation. It was compiled with configuration
option --with-pymalloc.

Without this option python-ldap runs fine with Python 2.1.1 and
2.2b2. :-)

Can somebody with C knowledge dig into that? At least python-ldap
build should failed if the Python interpreter was built with
--with-pymalloc.

Ciao, Michael.

incompatibility with pypgsql?

[Allan S. <as...@in...>]

Wondering if anyone has noted the following problem:

import ldap
from pyPgSQL import libpq

.
.
.

c = libpq.PQconnectdb(host, dbname, user, password)
Segmentation fault.

This is with pypgsql 2.2 and python-ldap-2.0.0-pre06.  The problem does 
not occur with python-ldap-2.0.0-pre04.

I did a "full featured" build of -pre06 (except for ldap_r) with 
openldap 2.0.23, contrary to the README instructions to use 2.0.26+, so 
that may be the problem.  Odd that it is affecting another library, 
though.

Allan

l_ldap_initialize enhancement

[<pe...@ha...>]

Hi

Here's a bug report I received in the debian tracker as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=179108

Could the patch in the bug logs please be applied upstream?

Thanks,
Peter
pe...@de...


--- Forwarded message ---

Hi,

While playing with python-ldap, I noticed a bad behaviour on an LDAP
server (long time to authenticate, probably DNS related) on a machine
over which I have no control.

I tried to circumvent this using the ldap_initilize(&foo, NULL)
equivalent on python-ldap... but I found that python-ldap lacks that
posibility.

Attached is a patch that enhances l_ldap_initialize, and
ldapobject.LDAPObject to support this. Maybe you or upstream are
interested on apply it.

Regards,
        Ricardo

--- Patch removed, see above url ---

Re: Lib/ldap.py missing - strange error message ...

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

Elsner wrote:
> warning: build_py: file Lib/ldap.py (for module ldap) not found
> warning: build_py: file Lib/ldap/schema.py (for module ldap.schema) not 
> found

ldap and ldap.schema are both module packages (directories containing 
various sub-modules). The messages above are falsely produced by DistUtils.

Don't worry about it. Just try if it works after install:

$ python -c "import ldap,ldap.schema;print ldap.__version__"

Ciao, Michael.

Lib/ldap.py missing - strange error message ...

[Elsner <Fra...@rz...>]

Trying to build, I get the following warnings:

[root@fleance python-ldap-2.0.0pre06]# python2 setup.py build
running build
running build_py
warning: build_py: file Lib/ldap.py (for module ldap) not found
warning: build_py: file Lib/ldap/schema.py (for module ldap.schema) 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/cidict.py (output up-to-date)
not copying Lib/ldap/functions.py (output up-to-date)
not copying Lib/ldap/sasl.py (output up-to-date)
not copying Lib/ldap/schema/__init__.py (output up-to-date)
not copying Lib/ldap/schema/tokenizer.py (output up-to-date)
not copying Lib/ldap/schema/models.py (output up-to-date)
not copying Lib/ldap/schema/subentry.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
warning: build_py: file Lib/ldap/schema.py (for module ldap.schema) not found
running build_ext
skipping '_ldap' extension (up-to-date)
----

Lib/ldap.py does not exist, anyway. Could you explain if this is an error
or a feature. Python2 is installed and working, OpenLDAP 2.12
is installed, too.

Regards Frank Elsner
#-------------------------------------------------------#
Dipl.-Math. Frank Elsner
Universitaet Osnabrueck (University of Osnabrueck)
- Rechenzentrum - (Computing Center)
Albrechstrasse 28, AVZ
D-49076 Osnabrueck
Deutschland (Germany)

Tel. (Phone): ++49 (0)541/969-2343 Fax: -2470
E-Mail: Fra...@rz...
#-------------------------------------------------------#

Mem leaks in current

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

HI!

Could someone with C knowledge please volunteer checking for mem leaks in 
l_ldap_search_ext() (see LDAPObject.c in CVS)?

Ciao, Michael.

forwarded bug report

[<pha...@tr...>]

Hi...

I'm just forwarding a bug report I received through the debian BTS.
I think the reporter is correct, so could you please apply this patch
upstream?

Thanks,
Peter

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=175710
-- Forwarded message --

hi Peter,

the problem is that in ldap.modlist.modifyModlist() new_value gets
filtered while old_value doesn't.

exploting: user passes a empty list as value of an attribute.
modifyModlist() sees this attribute in the new_value and filter it.

later, seeing it missing from the new entry, modifyModlist thinks it
is the case to schedule it for removal. after modifyModlist() returns
the user puts aside this entry for later use.

after having changed the value for that attribute, he wants to commit
it. he takes his old and new entries and calls modifyModlist. this
time the old empty value is not filtered! seeing differences between
the old and the new, modifyModlist will choose to delete (again) the
old attribute's value and add the new. but ldap server has not any old
value because that attribute has been already deleted by the previous
call, and an exceptinon is raised.

the fix is simple, i attached a patch.

a quick workaround for those not having a fixed version is to filter
the old_entry by hand, before calling modifyModlist().

cheers
cavok

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux ingiusta 2.4.18-cavok #1 Wed May 15 16:41:15 CEST 2002
i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages python2.2-ldap depends on:
ii  libc6                         2.3.1-9    GNU C Library: Shared libraries an
ii  libldap2                      2.0.27-3   OpenLDAP libraries (without TLS su
ii  libsasl7                      1.5.27-3.3 Authentication abstraction library
ii  python2.2                     2.2.2-4    An interactive object-oriented scr

-- no debconf information

-----[ Domenico Andreoli, aka cavok
 --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

--zhXaljGHf11kAtnf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="modlist-0.1.0.py.patch"

--- /usr/lib/python2.2/site-packages/ldap/modlist.py	2002-09-18 16:04:47.000000000 +0200
+++ modlist.py	2003-01-07 16:33:22.000000000 +0100
@@ -75,6 +75,7 @@
     new_value = filter(None,new_entry[attrtype])
     if attrtype_lower_map.has_key(attrtype_lower):
       old_value = old_entry.get(attrtype_lower_map[attrtype_lower],[])
+      old_value = filter(None,old_value)
       del attrtype_lower_map[attrtype_lower]
     else:
       old_value = []

--zhXaljGHf11kAtnf--

>>15.2 MILLION EMAIL ADDRESSES...PLUS $2,000 IN FREE EMAIL MARKETING SOFTWARE!

[Brigowen<cyb...@ya...>]

WOULD YOU LIKE TO HAVE YOUR MESSAGE SEEN BY OVER
15.1 MILLION TARGETED PROSPECTS DAILY?

Below contains all the information you will ever need to market your product or 
service on the Internet.

If you have a product, service, or message that you would like to get out 
to Thousands, Hundreds of Thousands, or even Millions of people, you 
have several options. Traditional methods include print advertising, direct 
mail, radio, and television advertising. They are all effective, but they all 
have two catches: They're EXPENSIVE and TIME CONSUMING. Not 
only that, you only get ONE SHOT at making your message heard by 
the right people. Also, Internet Search Engine Submissions, Classified Ads, 
Newsgroup Postings simply DO NOT WORK effectively.

Now this has all changed!

Thanks to the top programmers in the world and their NEW EMAIL
TECHNOLOGY, You can send millions of email messages daily for 
FREE...Without getting terminated from your current Internet connection!

It's very simple to do and you can be increasing your sales within minutes 
of installing this new extraordinary software!

Besides...It's the only real way to advertise on the Internet that works...Period!

>>>WE WILL SUPPLY YOU WITH OVER 15.1 MILLION OPT-IN EMAIL 
ADDRESSES TO GET YOU STARTED RIGHT AWAY!

>>>PLUS FREE EMAIL ADDRESS DOWNLOADS FOR LIFE!

>>>ALSO, YOU WILL RECEIVE $2,000 WORTH OF EMAIL 
MARKETING SOFTWARE FREE!

Including......

BROADCAST EMAIL SENDING SOFTWARE...(send millions of email 
advertisements daily with a few clicks of your mouse, without getting your
ISP trerminated. We used the same software to send you this email)

EMAIL EXTRACTION SOFTWARE...(retrieve new targeted email addresses 
daily. Hundreds of thousands of them)

LIST MANAGEMENT SOFTWARE...(keep your lists clean, opt-in and 
manage all your remove requests, leads, sales etc...)
 
and much...much more!

Hurry...This extraordinary offer ends at midnight tonight!

To find out more information, Do not respond by email. Instead, click 
on the link below or copy and paste the exact web site address below 
into your web browser.

http://www.vvorldvvideventures.com/504305/addresses.htm





______________________________________________________
Want to be removed from our email list?
You were sent this email because you used our Opt-in service.
We hope you enjoy reading our messages. However, if you'd rather 
not receive future e-mails from us, Go to
our remove page at http://www.vvorldvvideventures.com/504305/remove.htm
_______________________________________________________

further python-ldap RPM updates

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

Another bug crept into the RPMs I built. A patch suggested by rread has 
been accepted for the 7.3 and 8.0 editions of the python-ldap RPM. It 
addresses incorrect permissions on the schema subdirectory. Updated 
RPMs and SRPMs have been posted to ftp.open-it.org. I'll also be 
looking at using "distutil install" shortly to make sure it can 
interact well with the spec file usage or pythondir (used to specify 
the version to build against).

Also, as soon as I dig out of the post holiday mess, I'm going to 
fulfill a promise to start tracking again the latest OpenLDAP packages, 
with an RPM of OpenLDAP 2.1.10.

Re: python-ldap and updateref

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

thanks a bunch, i am now getting the correct ldap.REFERRAL exception :)

jens


On Tuesday, Dec 24, 2002, at 10:34 US/Eastern, Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>> i know for a fact that the referral is not handled internally, the=20
>> entry on the master never gets changed. at this point i am not=20
>> entirely sure if my slave is indeed configured correctly.
>
> If you use
>
> conn.set_option(ldap.OPT_REFERRALS,0)
> conn.manage_dsa_it(0) # this is the default
>
> and your server is configured correctly you should get an exception of=20=

> class ldap.REFERRAL.
>
>> P.S.: frohe weihnachten ;)
>
> Ah, yes. :-)
>
> Merry Christmas to all the list members and a happy New Year.
>
> Ciao, Michael.
>

Re: python-ldap and updateref

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

Jens Vagelpohl wrote:
> 
> i know for a fact that the referral is not handled internally, the entry 
> on the master never gets changed. at this point i am not entirely sure 
> if my slave is indeed configured correctly.

If you use

conn.set_option(ldap.OPT_REFERRALS,0)
conn.manage_dsa_it(0) # this is the default

and your server is configured correctly you should get an exception of class 
ldap.REFERRAL.

> P.S.: frohe weihnachten ;)

Ah, yes. :-)

Merry Christmas to all the list members and a happy New Year.

Ciao, Michael.

Re: python-ldap and updateref

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

michael,

i know for a fact that the referral is not handled internally, the=20
entry on the master never gets changed. at this point i am not entirely=20=

sure if my slave is indeed configured correctly.

i did read in some unrelated documentation that how the referral is=20
handled differs based on the type of authentication you use. at this=20
moment i am using a simple bind.

jens

P.S.: frohe weihnachten ;)



On Tuesday, Dec 24, 2002, at 10:11 US/Eastern, Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>> i have done some testing by setting up a master and slave and using=20=

>> the "updateref" directive in the slave's slapd.conf. according to the=20=

>> OpenLDAP documentation that should cause the slave to hand back the=20=

>> URI designated in the updateref directive if someone attempts a >> =
write.
>> [..]
>> conn.set_option(ldap.OPT_DEREF, ldap.DEREF_ALWAYS)
>
> This option is for setting alias dereferencing which is something=20
> different.
>
>> but this does not seem to make a change.
>
> Maybe the OpenLDAP lib handles the referral internally and already=20
> changes the entry on your master?
>
> If you don't want to let the OpenLDAP lib handle the referral you have=20=

> to use:
>
> conn.set_option(ldap.OPT_REFERRALS,0)
>
> Ciao, Michael.
>

Re: python-ldap and updateref

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

Jens Vagelpohl wrote:
> 
> i have done some testing by setting up a master and slave and using the 
> "updateref" directive in the slave's slapd.conf. according to the 
> OpenLDAP documentation that should cause the slave to hand back the URI 
> designated in the updateref directive if someone attempts a write.
> [..]
> conn.set_option(ldap.OPT_DEREF, ldap.DEREF_ALWAYS)

This option is for setting alias dereferencing which is something different.

> but this does not seem to make a change.

Maybe the OpenLDAP lib handles the referral internally and already changes 
the entry on your master?

If you don't want to let the OpenLDAP lib handle the referral you have to use:

conn.set_option(ldap.OPT_REFERRALS,0)

Ciao, Michael.

python-ldap and updateref

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

for one of my python-ldap-based applications i am trying to make it 
behave correctly in a situation where it is talking to a slave that 
wants to defer to a master for certain updates.

i have done some testing by setting up a master and slave and using the 
"updateref" directive in the slave's slapd.conf. according to the 
OpenLDAP documentation that should cause the slave to hand back the URI 
designated in the updateref directive if someone attempts a write. 
however, it doesn't seem to work, at least from python-ldap. i can 
modify records on the slave all day long and it does not hand back the 
master's URI. at the python prompt, after binding with a suitable DN i 
also do...

conn.set_option(ldap.OPT_DEREF, ldap.DEREF_ALWAYS)

but this does not seem to make a change.

does anyone have this working with python-ldap? is my slave server 
configured incorrectly?

jens

Re: ldap_ufn_setfilter

[Rakesh N. <rn...@ze...>]

well this was solved when i copied the /zope/lib/python2.1/site-packages
folder with the /usr/lib/python2.1/site-packages
which basically has the ldapmodule which is written when pythin-ldap is
compiled.....


thanks, michael..


----- Original Message -----
From: "Michael Ströder" <mi...@st...>
To: "Rakesh Naidu" <rn...@ze...>
Cc: "Python Developer List" <pyt...@li...>
Sent: Friday, December 20, 2002 9:07 PM
Subject: Re: ldap_ufn_setfilter


> Rakesh Naidu wrote:
> > ImportError:
> > /home/zeo/zope/lib/python/Products/LDAPUserFolder/_ldapmodule.so:
undefined
> > symbol: ldap_ufn_setfilter
>
> Which version of python-ldap are you using and which LDAP lib?
>
> The filename _ldapmodule.so looks like 1.x but the UFN-related
> functions/methods were removed in 2.x.
>
> Ciao, Michael.
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
> Time is running out!  Thinkgeek.com has the coolest gifts for
> your favorite geek.   Let your fingers do the typing.   Visit Now.
> T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: ldap_ufn_setfilter

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

Michael Str=F6der wrote:
> Rakesh Naidu wrote:
>=20
>> python-ldap 2.0.0pre05 and libldap.so.2
>=20
> Really strange.

I digged into the mailing list archive and it seems that this problem was=
=20
solved quite a while ago. Please go for python-ldap 2.0.0pre06.

Ciao, Michael.

Re: ldap_ufn_setfilter

[Rakesh N. <rn...@ze...>]

        libldap.so.2 => /usr/lib/libldap.so.2 (0x40020000)
        liblber.so.2 => /usr/lib/liblber.so.2 (0x40049000)
        libm.so.6 => /lib/libm.so.6 (0x40053000)
        libc.so.6 => /lib/libc.so.6 (0x40075000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x4019b000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x401b2000)
        libdl.so.2 => /lib/libdl.so.2 (0x401c4000)
        libsasl.so.7 => /usr/lib/libsasl.so.7 (0x401c8000)
        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x401d3000)
        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x40200000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
        libdb-3.1.so => /usr/lib/libdb-3.1.so (0x402c9000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x40346000)
        libpam.so.0 => /lib/libpam.so.0 (0x40374000)

----- Original Message -----
From: "Michael Ströder" <mi...@st...>
To: "Rakesh Naidu" <rn...@ze...>
Cc: "Python Developer List" <pyt...@li...>
Sent: Friday, December 20, 2002 10:01 PM
Subject: Re: ldap_ufn_setfilter


> Rakesh Naidu wrote:
> > python-ldap 2.0.0pre05 and libldap.so.2
>
> Really strange. I don't believe the _ldapmodule.so is compiled from
> python-ldap 2.0.0pre05 sources.
>
> Is there a library mixture? Maybe an old python-ldap 1.x installation?
What does
>
> $ ldd home/zeo/zope/lib/python/Products/LDAPUserFolder/_ldapmodule.so
>
> say?
>
> Is there also a file called _ldap.so?
>
> Ciao, Michael.
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
> Time is running out!  Thinkgeek.com has the coolest gifts for
> your favorite geek.   Let your fingers do the typing.   Visit Now.
> T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: ldap_ufn_setfilter

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

Rakesh Naidu wrote:
> python-ldap 2.0.0pre05 and libldap.so.2

Really strange. I don't believe the _ldapmodule.so is compiled from 
python-ldap 2.0.0pre05 sources.

Is there a library mixture? Maybe an old python-ldap 1.x installation? What does

$ ldd home/zeo/zope/lib/python/Products/LDAPUserFolder/_ldapmodule.so

say?

Is there also a file called _ldap.so?

Ciao, Michael.

Re: ldap_ufn_setfilter

[Rakesh N. <rn...@ze...>]

python-ldap 2.0.0pre05 and libldap.so.2


----- Original Message -----
From: "Michael Ströder" <mi...@st...>
To: "Rakesh Naidu" <rn...@ze...>
Cc: "Python Developer List" <pyt...@li...>
Sent: Friday, December 20, 2002 9:07 PM
Subject: Re: ldap_ufn_setfilter


> Rakesh Naidu wrote:
> > ImportError:
> > /home/zeo/zope/lib/python/Products/LDAPUserFolder/_ldapmodule.so:
undefined
> > symbol: ldap_ufn_setfilter
>
> Which version of python-ldap are you using and which LDAP lib?
>
> The filename _ldapmodule.so looks like 1.x but the UFN-related
> functions/methods were removed in 2.x.
>
> Ciao, Michael.
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
> Time is running out!  Thinkgeek.com has the coolest gifts for
> your favorite geek.   Let your fingers do the typing.   Visit Now.
> T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: ldap_ufn_setfilter

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

Rakesh Naidu wrote:
> ImportError:
> /home/zeo/zope/lib/python/Products/LDAPUserFolder/_ldapmodule.so: undefined
> symbol: ldap_ufn_setfilter

Which version of python-ldap are you using and which LDAP lib?

The filename _ldapmodule.so looks like 1.x but the UFN-related 
functions/methods were removed in 2.x.

Ciao, Michael.

ldap_ufn_setfilter

[Rakesh N. <rn...@ze...>]

hi micheal,
i am getting this error now...
do you know why this is...

ImportError:
/home/zeo/zope/lib/python/Products/LDAPUserFolder/_ldapmodule.so: undefined
symbol: ldap_ufn_setfilter

regards,

Rakesh.


----- Original Message -----
From: "Michael Ströder" <mi...@st...>
To: "Rakesh Naidu" <rn...@ze...>
Cc: "python-ldap" <pyt...@li...>
Sent: Tuesday, December 17, 2002 4:52 PM
Subject: Re: error installing ldapmodule1.8


> Rakesh Naidu wrote:
> > michael...can u throw some light on this error.....
> >
> > 2002-12-17T10:50:45 ERROR(200) Zope Could not import
Products.LDAPUserFolder
> > Traceback (innermost last):
> > [..]
> > ImportError: No module named ldap
>
> This was recently discussed here. I've attached a posting by Jens before
he
> has to repeat it.
>
> Furthermore you can search the mailing list archive for 'Zope'.
>
> Ciao, Michael
>
> -------- Original Message --------
> Subject: Re: Problems importing ldap in Zope
> Date: Fri, 29 Nov 2002 20:12:57 -0500
> From: Jens Vagelpohl <je...@zo...>
> To: Jorge Loureiro Dias <lou...@dt...>
> CC: pyt...@li...
>
> this problem has nothing to do with zope. the ldap module zope is
> trying to import is messed up. the one zope is trying to import is most
> likely not the same one that gets imported if you run python itself
> from the command line.
>
> you need to locate the exact python binary zope uses and rebuild the
> python-ldap module with that binary.
>
> jens
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: Comment on documentation

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

Ganesan R wrote:
> 
> Oops, that should be modlist. 

I noticed that.

Ciao, Michael.