python-ldap-dev — discussion among developers

Re: ANN: Python-LDAP 2.0.0pre02

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

michael,

hm... very interesting. the lib directory was not in ld.so.conf. i'm=20
surprised it never failed before... now everything seems OK.

thanks!

jens


On Friday, February 1, 2002, at 08:06 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>>
>>>>> import ldap
>> Traceback (most recent call last):
>>    File "<stdin>", line 1, in ?
>>    File "/usr/local/lib/python2.1/site-packages/ldap/__init__.py", =
line=20
>> 5,
>> in ?
>>      from _ldap import *
>> ImportError: liblber.so.2: cannot load shared object file: No such =
file=20
>> or
>> directory
>>>>>
>>
>> i'm on YellowDog linux 2.1 (a redhat 7 clone for mac) with OpenLDAP =
2.0.
>> 18
>> and Python2.1.2. the messages from setup.py build and setup.py =
compile=20
>> did
>> not contain any errors during compilation.
>>
>> is it just my setup or is there a problem? this worked fine with the
>> previous release candidate you put on the sourceforge file list.
>
> This seems to be a problem with your OpenLDAP 2 shared libs. Check
> shared libs with
>
> $ ldd [Python lib dir]/site-packages/_ldap.so
>
> Make sure you have either configured /etc/ld.so.conf (invoke
> ldconfig after modifications) to contain directory lib/ of your
> local OpenLDAP 2 installation or set LD_LIBARY_PATH accordingly.
>
> If that does help since your on Mac architecture there might be
> other subtle problems I don't know of.
>
> Ciao, Michael.

Re: ANN: Python-LDAP 2.0.0pre02

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

Jens Vagelpohl wrote:
> 
>  >>> import ldap
> Traceback (most recent call last):
>    File "<stdin>", line 1, in ?
>    File "/usr/local/lib/python2.1/site-packages/ldap/__init__.py", line 5,
> in ?
>      from _ldap import *
> ImportError: liblber.so.2: cannot load shared object file: No such file or
> directory
>  >>>
> 
> i'm on YellowDog linux 2.1 (a redhat 7 clone for mac) with OpenLDAP 2.0.18
> and Python2.1.2. the messages from setup.py build and setup.py compile did
> not contain any errors during compilation.
> 
> is it just my setup or is there a problem? this worked fine with the
> previous release candidate you put on the sourceforge file list.

This seems to be a problem with your OpenLDAP 2 shared libs. Check
shared libs with

$ ldd [Python lib dir]/site-packages/_ldap.so

Make sure you have either configured /etc/ld.so.conf (invoke
ldconfig after modifications) to contain directory lib/ of your
local OpenLDAP 2 installation or set LD_LIBARY_PATH accordingly.

If that does help since your on Mac architecture there might be
other subtle problems I don't know of.

Ciao, Michael.

Re: ANN: Python-LDAP 2.0.0pre02

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

hi michael,

i'm getting this:

 >>> import ldap
Traceback (most recent call last):
   File "<stdin>", line 1, in ?
   File "/usr/local/lib/python2.1/site-packages/ldap/__init__.py", line =
5,=20
in ?
     from _ldap import *
ImportError: liblber.so.2: cannot load shared object file: No such file =
or=20
directory
 >>>

i'm on YellowDog linux 2.1 (a redhat 7 clone for mac) with OpenLDAP =
2.0.18=20
and Python2.1.2. the messages from setup.py build and setup.py compile =
did=20
not contain any errors during compilation.

is it just my setup or is there a problem? this worked fine with the=20
previous release candidate you put on the sourceforge file list.

jens



On Friday, February 1, 2002, at 07:36 , Michael Str=F6der wrote:

> HI!
>
> Another pre-release version of python-ldap is available at
>
>   http://sourceforge.net/project/showfiles.php?group_id=3D2072
>
> Please test!
>
> Ciao, Michael.
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

ANN: Python-LDAP 2.0.0pre02

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

HI!

Another pre-release version of python-ldap is available at

  http://sourceforge.net/project/showfiles.php?group_id=2072

Please test!

Ciao, Michael.

Re: ldapthreadlock.py and web2ldap

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

jha...@n2... wrote:
> 
> Hi! Just wanted to note that ldapthreadlock.py is still used
> by the application web2lap. It looks like ldapthreadlock.py has
> been removed from the cvs distribution. I was able to download a
> copy from CVS's Attic, but you may want to consider keeping it
> in the distribution or telling the web2ldap developers to use
> other methods.

Hmm, I'm also the author of web2ldap. Seems that I should make a new
web2ldap release...

Try the new snapshot of web2ldap. It has many new features and fixes
and runs quite stable.

Ciao, Michael.

ldapthreadlock.py and web2ldap

[<jha...@n2...>]

Hi! Just wanted to note that ldapthreadlock.py is still used by the =
application web2lap. It looks like ldapthreadlock.py has been removed =
from the cvs distribution. I was able to download a copy from CVS's =
Attic, but you may want to consider keeping it in the distribution or =
telling the web2ldap developers to use other methods.

Thanks,
Jen Hamilton

Re: why didn't it work?

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

Jens Vagelpohl wrote:
> 
> well, i did see all those messages on the list but none of them say
> anything about "import _ldap" being deprecated, and there was no mentioning
> of "there's new code examples, make sure your code follows them. or no one
> ever said "don't use the exisiting docs, they are wrong".

You definitely ignored my requests to test the code. There was no
feedback at all from the people complaining now.

> basically, there was a lot of talk about changes but none about the
> implications for people who use the python-ldap module.

We're talking about the CVS version. If there should still be any
progress possible with python-ldap it should be allowed to change
things. I'm trying my best to preserve backwards compability but off
course it needs testing. If folks are even too lazy to do very
simple tests I can't help. Note that in your case the only fix
needed is to import ldap instead _ldap. This should not be too hard
for you.

> i suppose i could have pored over all the attached code and looked for it.
> .. (my attempt at irony)

Yes, you should have glanced over this code or stay away from using
a developer version.

> don't get me wrong, i appreciate all the work that you're putting into it.

Blah.

>   i only got peeved because people started bitching at me about my products
> no longer working because i had no warning :P  the first thing out of my
> mouth was something like "wow, your python-ldap module must be really f*d
> up..."

Feel free to jump on in and do a better job. It's free software, not
free beer.

Michael.

Re: signature of ldap.open changed?

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

Jens Vagelpohl wrote:
> 
> now that i got beyond the changed importing semantics i notice that the
> "open" call to open a new connection has a *different* signature?

AFAIK there's no such thing as a "signature" in Python.

> can someone explain what the reasoning is? and, what's even more important,
>   how is anyone supposed to support both versions and test for them
> successfully in the code without some really ugly workarounds?

I have to admit I've never used open() in that way. I've checked in
a modified version compliant to the old docs.

Michael.

signature of ldap.open changed?

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

now that i got beyond the changed importing semantics i notice that the 
"open" call to open a new connection has a *different* signature?

can someone explain what the reasoning is? and, what's even more important,
  how is anyone supposed to support both versions and test for them 
successfully in the code without some really ugly workarounds?

again, i don't see this documented anywhere unless i actually step into 
the code or notice the module spewing uncontrollable debug messages onto 
the console because what i pass in as the port number all of a sudden gets 
interpreted as a trace level...

jens

Re: why didn't it work?

[Peeyush G. <pee...@ka...>]

Michael,

Your links point to mailing archives of around Dec 21, 2001. But, I checked
out the LDAP module somewhere around Jan 3rd, 2002 and that's the code they
contained. But, possibly I might have used the wrong command while checking
out the module. I'll try it again. Thanks for the info.

~Peeyush.
----- Original Message -----
From: "Michael Ströder" <mi...@st...>
To: "Jens Vagelpohl" <je...@zo...>
Cc: <pyt...@li...>
Sent: Tuesday, January 29, 2002 12:21 AM
Subject: Re: why didn't it work?


> 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.
>
> http://www.geocrawler.com/mail/msg.php3?msg_id=7383302&list=1568
>
>
http://www.geocrawler.com/mail/thread.php3?subject=Stripped+LDAPObject.c&lis
t=1568
>
> 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.
>
> Ciao, Michael.
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: why didn't it work?

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

well, i did see all those messages on the list but none of them say=20
anything about "import _ldap" being deprecated, and there was no =
mentioning=20
of "there's new code examples, make sure your code follows them. or no =
one=20
ever said "don't use the exisiting docs, they are wrong".

basically, there was a lot of talk about changes but none about the=20
implications for people who use the python-ldap module.

i suppose i could have pored over all the attached code and looked for =
it.
.. (my attempt at irony)

don't get me wrong, i appreciate all the work that you're putting into =
it.
  i only got peeved because people started bitching at me about my =
products=20
no longer working because i had no warning :P  the first thing out of my=20=

mouth was something like "wow, your python-ldap module must be really =
f*d=20
up..."

jens


On Tuesday, January 29, 2002, at 03:21 , Michael Str=F6der wrote:

> 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.
>
> http://www.geocrawler.com/mail/msg.php3?msg_id=3D7383302&list=3D1568
>
> =
http://www.geocrawler.com/mail/thread.php3?subject=3DStripped+LDAPObject.c=
&
> list=3D1568
>
> 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.
>
> Ciao, Michael.

Re: why didn't it work?

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

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.

http://www.geocrawler.com/mail/msg.php3?msg_id=7383302&list=1568

http://www.geocrawler.com/mail/thread.php3?subject=Stripped+LDAPObject.c&list=1568

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.

Ciao, Michael.

Re: why didn't it work?

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

actually it does not work well in the latest python-ldap. importing =
_ldap=20
will not raise an ImportError. but _ldap is crippled and will blow up =
the=20
first time you try to call something with it.

everywhere i go on the python-ldap.sourceforge.net site the docs talk of=20=

the "_ldap" module and code examples use "import _ldap". that's probably=20=

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=20=

ldap is the only way it works.

jens



On Monday, January 28, 2002, at 01:52 , Peeyush Garg wrote:

> As I see it in the latest code, I think both shud work....
>
> try:
>     import _ldap
> except ImportError:
>     import ldap
>     _ldap =3D ldap
>
> Except I couldn't still get it running either way on Unix but runs=20
> perfectly
> on Windows even though it installs correctly on Unix. I tried Zope =
mailing
> list too. No luck.
>
> ~Peeyush.
>
> ----- Original Message -----
> From: "Jens Vagelpohl" <je...@zo...>
> To: <mi...@st...>
> Cc: "python-ldap-dev" <pyt...@li...>
> Sent: Monday, January 28, 2002 7:57 AM
> Subject: Re: why didn't it work?
>
>
> i'm very surprised. i was under the impression that it was just the =
other
> way around: importing _ldap was the canonical way and importing ldap =
only
> existed for backwards compatibility.
>
> i'm confused.
>
> jens
>
>
> On Monday, January 28, 2002, at 10:29 , Michael Str=F6der wrote:
>
>> Jens Vagelpohl wrote:
>>>
>>> i'm getting complaints about this from people who use some of my=20
>>> products
>>> that rely on python-ldap. one guy uses a CVS checkout from january =
4th.
>>> is
>>> the CVS version hosed?
>>
>> Don't import _ldap. Despite some code examples this was never good
>> practice.
>>
>>> if I try to call the "_ldap.open" function, it fails :
>>> module _ldap does not have such function.
>>
>> Yes.
>>
>>>>>> can you import "ldap"?
>>> Yes, I can, and I can call functions "ldap.open", "ldap.bind_s", =
etc.
>>> *******
>>
>> There's no reason to import _ldap. Don't do that. Everything's
>> wrapped correctly in module ldap.ldapobject.
>>
>> Ciao, Michael.
>
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: why didn't it work?

[Peeyush G. <pee...@ka...>]

As I see it in the latest code, I think both shud work....

try:
    import _ldap
except ImportError:
    import ldap
    _ldap = ldap

Except I couldn't still get it running either way on Unix but runs perfectly
on Windows even though it installs correctly on Unix. I tried Zope mailing
list too. No luck.

~Peeyush.

----- Original Message -----
From: "Jens Vagelpohl" <je...@zo...>
To: <mi...@st...>
Cc: "python-ldap-dev" <pyt...@li...>
Sent: Monday, January 28, 2002 7:57 AM
Subject: Re: why didn't it work?


i'm very surprised. i was under the impression that it was just the other
way around: importing _ldap was the canonical way and importing ldap only
existed for backwards compatibility.

i'm confused.

jens


On Monday, January 28, 2002, at 10:29 , Michael Ströder wrote:

> Jens Vagelpohl wrote:
>>
>> i'm getting complaints about this from people who use some of my products
>> that rely on python-ldap. one guy uses a CVS checkout from january 4th.
>> is
>> the CVS version hosed?
>
> Don't import _ldap. Despite some code examples this was never good
> practice.
>
>> if I try to call the "_ldap.open" function, it fails :
>> module _ldap does not have such function.
>
> Yes.
>
>>>>> can you import "ldap"?
>> Yes, I can, and I can call functions "ldap.open", "ldap.bind_s", etc.
>> *******
>
> There's no reason to import _ldap. Don't do that. Everything's
> wrapped correctly in module ldap.ldapobject.
>
> Ciao, Michael.


_______________________________________________
Python-LDAP-dev mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: why didn't it work?

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

i'm very surprised. i was under the impression that it was just the =
other=20
way around: importing _ldap was the canonical way and importing ldap =
only=20
existed for backwards compatibility.

i'm confused.

jens


On Monday, January 28, 2002, at 10:29 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>>
>> i'm getting complaints about this from people who use some of my =
products
>> that rely on python-ldap. one guy uses a CVS checkout from january =
4th.=20
>> is
>> the CVS version hosed?
>
> Don't import _ldap. Despite some code examples this was never good
> practice.
>
>> if I try to call the "_ldap.open" function, it fails :
>> module _ldap does not have such function.
>
> Yes.
>
>>>>> can you import "ldap"?
>> Yes, I can, and I can call functions "ldap.open", "ldap.bind_s", etc.
>> *******
>
> There's no reason to import _ldap. Don't do that. Everything's
> wrapped correctly in module ldap.ldapobject.
>
> Ciao, Michael.

Re: why didn't it work?

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

Jens Vagelpohl wrote:
> 
> i'm getting complaints about this from people who use some of my products
> that rely on python-ldap. one guy uses a CVS checkout from january 4th. is
> the CVS version hosed?

Don't import _ldap. Despite some code examples this was never good
practice.

> if I try to call the "_ldap.open" function, it fails :
> module _ldap does not have such function.

Yes.

>  >>> can you import "ldap"?
> Yes, I can, and I can call functions "ldap.open", "ldap.bind_s", etc.
> *******

There's no reason to import _ldap. Don't do that. Everything's
wrapped correctly in module ldap.ldapobject.

Ciao, Michael.

Re: why didn't it work?

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

i'm getting complaints about this from people who use some of my products 
that rely on python-ldap. one guy uses a CVS checkout from january 4th. is 
the CVS version hosed?

*****
 >>> if you launch python, can you import "_ldap"?
Yes, I can, but if I try to call the "_ldap.open" function, it fails : 
module _ldap does not have such function.

 >>> can you import "ldap"?
Yes, I can, and I can call functions "ldap.open", "ldap.bind_s", etc.
*******

jens



On Monday, January 28, 2002, at 10:42 , dino wrote:

> Many tanks to you and other people that work for opensource!!!
> I built latest version of python ldap module.
> It works only if I import ldap, not _ldap. Why?
> Thanks a lot for working and, I am di...@pr..., italian guy. Bye.
>

why didn't it work?

[dino <di...@pr...>]

Many tanks to you and other people that work for opensource!!!
I built latest version of python ldap module.
It works only if I import ldap, not _ldap. Why?
Thanks a lot for working and, I am di...@pr..., italian guy. Bye.

Re: Python-ldap on windows

[Jason T. <ja...@ti...>]

Thomas,

On Fri, Jan 25, 2002 at 08:39:11AM +0100, Thomas Heller wrote:
> From: "Michael Ströder" <mi...@st...>
> > cygwin-version announced by Jason on the list recently?
> 
> I don't run cygwin (and I've just at the moment subscribed to this list).

Just in case you are interested in a Cygwin python-ldap, see the
following:

    http://www.geocrawler.com/archives/3/1568/2002/1/0/7452037/

Jason

Re: Python-ldap on windows

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

Thomas Heller wrote:
> 
> I had mixed windows binaries
> with current CVS code.

The Win32 binaries are probably build against old Umich libs. There
is no recent version of python-ldap linked against OpenLDAP 2 libs
for native Win32 (only cygwin). python-ldap based on Umich libs does
not provide support for SSL or StartTLS.

> BTW: What I'm trying to do is to write a Python script which
> imports a csv file (exported from a database we have here with
> contact information: name, address, email, telphone number...)
> into a LDAP server. Is there any previous work which could help
> me getting started?

IMHO there's a csv module for Python. You should map the table
columns to attributes and build an entry dictionary. You can either
write this to the LDAP server by converting the entry's dict with
ldap.modlist.addModlist() to a modify list you can directly pass to
add_s() method or diff against existing entries with
ldap.modlist.modifyModlist().
Hmm, module ldap.modlist is only available in recent CVS version.
You can extract it from there and back-port it to old version
though. It does not directly rely on something else except some
constants.

You can also create LDIF with module ldif for bulk-upload into your
LDAP server with some command-line tools. Recent version of module
ldif in CVS is also improved.

Ciao, Michael.

Re: Python-ldap on windows

[Thomas H. <tho...@io...>]

From: "Michael Str=F6der" <mi...@st...>
> Thomas Heller wrote:
> >
> > What's the status on windows? I have downloaded the binaries,
> > but they don't seem to work too well.
>
> Which binaries? What's missing? What's wrong? Did you check out

Well, I spoke too soon. My problems were a) that I did not know
exactly what I was doing, and b) that I had mixed windows binaries
with current CVS code.

BTW: What I'm trying to do is to write a Python script which
imports a csv file (exported from a database we have here with
contact information: name, address, email, telphone number...)
into a LDAP server. Is there any previous work which could help
me getting started?

> cygwin-version announced by Jason on the list recently?

I don't run cygwin (and I've just at the moment subscribed to this list).

Thanks,

Thomas

Re: Python-ldap on windows

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

Thomas Heller wrote:
> 
> What's the status on windows? I have downloaded the binaries,
> but they don't seem to work too well.

Which binaries? What's missing? What's wrong? Did you check out
cygwin-version announced by Jason on the list recently?

Ciao, Michael.

Python-ldap on windows

[Thomas H. <tho...@io...>]

Hi.

What's the status on windows? I have downloaded the binaries,
but they don't seem to work too well.

Regards,

Thomas

FYI: manage_dsa_it()

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

HI!

I've added a new method LDAPObject.manage_dsa_it() for
enabling/disabling manage DSA IT mode for adding/modifying referral
entries (see draft-zeilenga-ldap-namedref).

It's just a dirty hack as long there's no full support for extended
controls. It might change silently.

Ciao, Michael.

Re: Complining on SunOS 5.8

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

Manuel Tilp wrote:
> 
> I try to build 1.10alpha3, but i get a lot of warnings like this
> one:
> "/python-ldap-1.10alpha3/Modules/./template.c:143: warning:
> function declaration isn't a prototype"
> ( in template.c and linkedlist.c, configure seems to work fine ).
> 
> I also tried CVS200201041716, but when doing "python2.1 setup.py
> install" gcc fails to compile
> constants.c after dozens of
> 'LDAP_XYZ' undeclared (first use in this function)
> error-messages.

You need OpenLDAP libs 2.0.13+ for this snapshot. You also need to
use --with-tls when compiling the OpenLDAP 2 libs.

> Everything worked fine on a Linuxbox, but that doesn't help me..

Which version of the OpenLDAP libs do you have on your Linux and
your SunOS box? Compiling against the LDAP libs shipped with SunOS
very likely doesn't work (at least with recent snapshot).

Ciao, Michael.