python-ldap-dev — discussion among developers

Re: Problem with names that include ","

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

Marc Balmer wrote:
> take a look at RFC 1779.  A semicolon could be used as an
> alternate delimiter and it shuld be possible to enclose strings
> in quotes, i.e. like this:

RFC 1779 was part of LDAPv2 standard which has been obsoleted for quite
a while now. Today RFC 4514 is relevant for LDAPv3-based DSAs which does
not allow semicolon as delimiter.

Ciao, Michael.

Re: Problem with names that include ","

[Marc B. <ma...@ms...>]

Am 02.06.2009 um 13:13 schrieb Christoph Holtermann:

> Hello !
>
> Thanks for your reply and that of Marc Balmer.
> But I still wonder if it is allowed by LDAP or LDIF-
> Specification to have a comma in dn. I also tried it
> with "" and Base64, some of which
> openldap accepted.

take a look at RFC 1779.  A semicolon could be used as an
alternate delimiter and it shuld be possible to enclose strings
in quotes, i.e. like this:

dn="Balmer, Marc",ou=research,dc=msys,dc=ch

But I did not test if OpenLDAP "eats" this... ;)

- Marc Balmer

>
> C. Holtermann
>
> Yves Dorfsman schrieb:
>>
>> Christoph Holtermann wrote:
>>
>>
>>> I am working on a filter that makes Thunderbirds LDIF-Output
>>> importable to OpenLDAP. It works quite fine except for names
>>> that include ",". OpenLDAP dislikes the output that is produced
>>> like :
>>>
>>> dn: cn=Lehmann\, Veronika,dc=Adressbuch,dc=christoph
>>>
>>
>> Escaping characters is used by some LDAP servers, not all of them,  
>> but is
>> not conform to LDIF.
>>
>>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the  
> latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get_______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: Problem with names that include ","

[Christoph H. <c.h...@gm...>]

Hi !
>>
>> Thanks for your reply and that of Marc Balmer.
>> But I still wonder if it is allowed by LDAP or LDIF-
>> Specification to have a comma in dn. I also tried it
>> with "" and Base64, some of which
>> openldap accepted.
>
> take a look at RFC 1779.  A semicolon could be used as an
> alternate delimiter and it shuld be possible to enclose strings
> in quotes, i.e. like this:
>
> dn="Balmer, Marc",ou=research,dc=msys,dc=ch
>
> But I did not test if OpenLDAP "eats" this... ;)
>
> - Marc Balmer
>
I just fed it with

dn: cn="Lehmann, Veronika",dc=Adressbuch,dc=christoph
objectclass: top
objectclass: person
objectclass: inetOrgPerson
objectclass: mozillaAbPersonAlpha
sn: Lehmann
cn: Lehmann, Veronika

it works fine. But the Output of OpenLDAP, when I ldapsearch it is :

> ldapsearch -x "(cn=*lehmann*)"
# extended LDIF                                                    
#                                                                  
# LDAPv3                                                           
# base <dc=christoph> (default) with scope subtree                 
# filter: (cn=*lehmann*)                                           
# requesting: ALL                                                  
#

# Lehmann\2C Veronika, Adressbuch.christoph
dn: cn=Lehmann\2C Veronika,dc=Adressbuch,dc=christoph
objectClass: top
objectClass: person
objectClass: inetOrgPerson
objectClass: mozillaAbPersonAlpha
sn: Lehmann
cn: Lehmann, Veronika

And what I saw was : escape-codes. And I just have been told, that
it's not LDIF-conform ;-) probably they don't know ?
                                                       

So my goal now is to make my filter put entrys which contain commas
in "". Does anyone know how to make Python-ldap do so ?

C. Holtermann

Re: Problem with names that include ","

[Christoph H. <c.h...@gm...>]

Hello !

Thanks for your reply and that of Marc Balmer.
But I still wonder if it is allowed by LDAP or LDIF-
Specification to have a comma in dn. I also tried it
with "" and Base64, some of which
openldap accepted.

C. Holtermann

Yves Dorfsman schrieb:
> Christoph Holtermann wrote:
>
>   
>> I am working on a filter that makes Thunderbirds LDIF-Output
>> importable to OpenLDAP. It works quite fine except for names
>> that include ",". OpenLDAP dislikes the output that is produced
>> like :
>>
>> dn: cn=Lehmann\, Veronika,dc=Adressbuch,dc=christoph
>>     
>
> Escaping characters is used by some LDAP servers, not all of them, but is 
> not conform to LDIF.
>
>   

Re: problem with set_option and tls

[Mike L. <mi...@mo...>]

Michael Ströder wrote:
> Mike Lovell wrote:
>   
>> Michael Ströder wrote:
>>     
>>> I guess you're using python-ldap built against OpenLDAP 2.3 client libs.
>>> With OpenLDAP 2.4 connection-specific TLS options should be supported.
>>>
>>>   
>>>       
>> I am using a machine with Ubuntu 9.04 which has the 2.4 OpenLDAP
>> libraries.
>>     
>
> Please post the exact OpenLDAP version.
>
> Ciao, Michael.
>   
hopefully this is enough info for you.

mike@thor:~/Desktop$ dpkg -l python-ldap libldap*
ii  libldap-2.4-2  2.4.15-1ubuntu OpenLDAP libraries
ii  python-ldap    2.3.5-1ubuntu1 An LDAP interface module for Python

mike@thor:~/Desktop$ ldd /usr/lib/python2.6/dist-packages/_ldap.so
    linux-vdso.so.1 =>  (0x00007fff5b1ff000)
    libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 (0x00007f8252b90000)
    liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007f8252981000)
    libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00007f8252766000)
    libpthread.so.0 => /lib/libpthread.so.0 (0x00007f825254a000)
    libc.so.6 => /lib/libc.so.6 (0x00007f82521d8000)
    libdl.so.2 => /lib/libdl.so.2 (0x00007f8251fd3000)
    libresolv.so.2 => /lib/libresolv.so.2 (0x00007f8251dbb000)
    libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0x00007f8251b0e000)
    libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0x00007f82518fc000)
    libz.so.1 => /lib/libz.so.1 (0x00007f82516e4000)
    libgcrypt.so.11 => /lib/libgcrypt.so.11 (0x00007f825147d000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f8253005000)
    libgpg-error.so.0 => /lib/libgpg-error.so.0 (0x00007f8251279000)

Re: Problem with names that include ","

[Yves D. <yv...@zi...>]

Christoph Holtermann wrote:

> I am working on a filter that makes Thunderbirds LDIF-Output
> importable to OpenLDAP. It works quite fine except for names
> that include ",". OpenLDAP dislikes the output that is produced
> like :
> 
> dn: cn=Lehmann\, Veronika,dc=Adressbuch,dc=christoph

Escaping characters is used by some LDAP servers, not all of them, but is 
not conform to LDIF.

-- 
Yves.
http://www.sollers.ca/

Problem with names that include ","

[Christoph H. <c.h...@gm...>]

Hello !

I am working on a filter that makes Thunderbirds LDIF-Output
importable to OpenLDAP. It works quite fine except for names
that include ",". OpenLDAP dislikes the output that is produced
like :

dn: cn=Lehmann\, Veronika,dc=Adressbuch,dc=christoph
cn: Lehmann\, Veronika
givenName: Lehmann,
mail: inf...@un...
objectClass: top
objectClass: person
objectClass: inetOrgPerson
objectClass: mozillaAbPersonAlpha
sn: Veronika

I found out that an encoding like "\2C" is accepted, like :

dn: cn=Lehmann\2C Veronika,dc=Adressbuch,dc=christoph
cn: Lehmann, Veronika
givenName: Lehmann,
mail: inf...@un...
objectClass: top
objectClass: person
objectClass: inetOrgPerson
objectClass: mozillaAbPersonAlpha
sn: Veronika

Thunderbird exported the entry like this :

dn: cn="Lehmann, Veronika",mail=inf...@un...
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
objectclass: mozillaAbPersonAlpha
givenName: Lehmann,
sn: Veronika
cn: "Lehmann, Veronika"
mail: inf...@un...
modifytimestamp: 0Z

This is about one of the last things that I have to change by
hand. Maybe someone can help me with this encoding problem.

The code that is about that problem looks like :

basedn='dc=Adressbuch,dc=christoph'

def fix_dn(self, dn):
 try:
  self.head=ldap.dn.explode_dn(dn)[0]
  for i in range(len(dn_warning)):
   if self.head.find(dn_warning[i])>-1:
    print "dn :",self.head, "contains '",dn_warning[i],"' - change
manually !"
  return self.head + ',' + basedn
 except:
  if dn==None:
   print "No dn specified"
   return None

regards,

C. Holtermann

Re: problem with set_option and tls

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

Mike Lovell wrote:
> Michael Ströder wrote:
>> I guess you're using python-ldap built against OpenLDAP 2.3 client libs.
>> With OpenLDAP 2.4 connection-specific TLS options should be supported.
>>
>>   
> I am using a machine with Ubuntu 9.04 which has the 2.4 OpenLDAP
> libraries.

Please post the exact OpenLDAP version.

Ciao, Michael.

Re: problem with set_option and tls

[Mike L. <mi...@mo...>]

Michael Ströder wrote:
> I guess you're using python-ldap built against OpenLDAP 2.3 client libs.
> With OpenLDAP 2.4 connection-specific TLS options should be supported.
>
>   
I am using a machine with Ubuntu 9.04 which has the 2.4 OpenLDAP 
libraries. I double checked the package dependencies and did ldd on the 
_ldap.so file and both show it was compiled against the 2.4 libraries. I 
am using python-ldap 2.3.5. I don't know if a newer version is needed 
for this. But I am planning on several Debian Etch machines which were 
built against older OpenLDAP libraries so I should still plan for this 
behavior. Thanks for the help.

mike

Re: problem with set_option and tls

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

Mike Lovell wrote:
> First off, hello everyone.
> I am working on some software that uses python-ldap that is trying to 
> connect to an ldaps server. If I do this sequence
> 
> import ldap
> ldap.set_option(ldap.OPT_X_TLS_CACERTFILE, '/path/to/cert')
> conn = ldap.initialize('ldaps://server')
> conn.simple_bind_s('uid', 'pass')
> 
> things work fine. But if I do it like this
> 
> import ldap
> conn = ldap.initialize('ldaps://server')
> conn.set_option(ldap.OPT_X_TLS_CACERTFILE, '/path/to/cert')
> conn.simple_bind_s('uid', 'pass')
> 
> then I get an error saying that it can't contact the server. I am 
> guessing it just can't verify the server's ssl certificate and just 
> saying it can't contact the server.

I guess you're using python-ldap built against OpenLDAP 2.3 client libs.
With OpenLDAP 2.4 connection-specific TLS options should be supported.

> Is this expected behavior? Is this a restriction of the underlying 
> openldap client libraries?

Yupp. Version-specific.

Ciao, Michael.

problem with set_option and tls

[Mike L. <mi...@mo...>]

First off, hello everyone.
I am working on some software that uses python-ldap that is trying to 
connect to an ldaps server. If I do this sequence

import ldap
ldap.set_option(ldap.OPT_X_TLS_CACERTFILE, '/path/to/cert')
conn = ldap.initialize('ldaps://server')
conn.simple_bind_s('uid', 'pass')

things work fine. But if I do it like this

import ldap
conn = ldap.initialize('ldaps://server')
conn.set_option(ldap.OPT_X_TLS_CACERTFILE, '/path/to/cert')
conn.simple_bind_s('uid', 'pass')

then I get an error saying that it can't contact the server. I am 
guessing it just can't verify the server's ssl certificate and just 
saying it can't contact the server. But it appears that if I set the 
option on the ldap module it works but setting the option on the 
individual connection doesn't.

Is this expected behavior? Is this a restriction of the underlying 
openldap client libraries? Or a bug that could use some attention? I am 
wanting to get it so that the options are on the connections so that I 
could do multiple connections with different options. Thanks for any 
help in advance.

mike

Re: LDIF Generation using Python-LDAP

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

Guruprasad wrote:
> Hi,
> 2009/5/16 Michael Ströder <mi...@st...>:
>> Guruprasad wrote:
>>> 2009/5/16 Michael Ströder <mi...@st...>:
>>>> Guruprasad wrote:
>>>>> Hi,
>>>>> I tried generating a LDIF file from a dictionary using 'ldif' module
>>>>> as illustrated in http://www.python-ldap.org/doc/html/ldif.html. But
>>>>> at the end of the LDIF data, I get a newline and a 'None', whereas
>>>>> there is no such thing in the result shown in that example. How to get
>>>>> rid of those unwanted characters. I am using Python-LDAP 2.3.5-1 on
>>>>> Debian Lenny.
>>>> Could you please post your code (in a short form) demonstrating the
>>>> issue? Note that there is a new-line after each entry record. But was
>>>> 'None' is in your case is not clear to me.
>>>>
>>> Basically what I am trying to do with this code is that, I manipulate
>>> the result returned by ldapsearch to remove some attributes and
>>> generate a LDIF output for the modified entry.
>>>
>>> <code>
>>>         res_type, result_data=l.result(res_id,0)
>>>         if (result_data==[]):
>>>             break
>>>         dn=result_data[0][0]
>>>       resd=result_data[0][1]
>>>         resd["objectClass"].remove("inetLocalMailRecipient")
>>>           resd["objectClass"].remove("organizationalPerson")
>>>           resd["objectClass"].remove("inetOrgPerson")
>>>         resd["objectClass"].remove("posixAccount")
>>>         lw=ldif.LDIFWriter(sys.stdout)
>>>       guru=lw.unparse(dn,resd)
>>>       print guru
>>> </code>
>> Your code looks like processing of LDAP search results (because of the
>> res_type). I'd recommend to look at the actual data in dictionary resd.
>> Also note that the identiation seems wrong. This could be because of
>> cut&paste to your MUA from the editor with different tab-interpretation.
>> But make sure identiation is correct in the real code.
> 
> The indentation is correct in the real code. The dictionary 'resd' has
> the values returned by the ldapsearch and there is no 'None' anywhere
> in it.

I think your interpretation of the output is wrong. Method
LDIFWrite.unparse() outputs the LDIF to the file object (in your case
sys.stdout). If you print the result of method unparse() that's
obviously None.

Ciao, Michael.

Re: LDIF Generation using Python-LDAP

[Guruprasad <lgp...@gm...>]

Hi,
2009/5/16 Michael Ströder <mi...@st...>:
> Guruprasad wrote:
>> 2009/5/16 Michael Ströder <mi...@st...>:
>>> Guruprasad wrote:
>>>> Hi,
>>>> I tried generating a LDIF file from a dictionary using 'ldif' module
>>>> as illustrated in http://www.python-ldap.org/doc/html/ldif.html. But
>>>> at the end of the LDIF data, I get a newline and a 'None', whereas
>>>> there is no such thing in the result shown in that example. How to get
>>>> rid of those unwanted characters. I am using Python-LDAP 2.3.5-1 on
>>>> Debian Lenny.
>>> Could you please post your code (in a short form) demonstrating the
>>> issue? Note that there is a new-line after each entry record. But was
>>> 'None' is in your case is not clear to me.
>>>
>>
>> Basically what I am trying to do with this code is that, I manipulate
>> the result returned by ldapsearch to remove some attributes and
>> generate a LDIF output for the modified entry.
>>
>> <code>
>>         res_type, result_data=l.result(res_id,0)
>>         if (result_data==[]):
>>             break
>>         dn=result_data[0][0]
>>       resd=result_data[0][1]
>>         resd["objectClass"].remove("inetLocalMailRecipient")
>>           resd["objectClass"].remove("organizationalPerson")
>>           resd["objectClass"].remove("inetOrgPerson")
>>         resd["objectClass"].remove("posixAccount")
>>         lw=ldif.LDIFWriter(sys.stdout)
>>       guru=lw.unparse(dn,resd)
>>       print guru
>> </code>
>
> Your code looks like processing of LDAP search results (because of the
> res_type). I'd recommend to look at the actual data in dictionary resd.
> Also note that the identiation seems wrong. This could be because of
> cut&paste to your MUA from the editor with different tab-interpretation.
> But make sure identiation is correct in the real code.
>
> Ciao, Michael.
>

The indentation is correct in the real code. The dictionary 'resd' has
the values returned by the ldapsearch and there is no 'None' anywhere
in it.


Thank you.

Regards,
Guruprasad.

Re: LDIF Generation using Python-LDAP

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

Guruprasad wrote:
> My ldapsearch query returns only one record. I have written such a filter.

Sorry, my crystal ball is a bit blurry. I can't help without really
knowing what you're trying to achieve.

Ciao, Michael.

Re: LDIF Generation using Python-LDAP

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

Guruprasad wrote:
> 2009/5/16 Michael Ströder <mi...@st...>:
>> Guruprasad wrote:
>>> Hi,
>>> I tried generating a LDIF file from a dictionary using 'ldif' module
>>> as illustrated in http://www.python-ldap.org/doc/html/ldif.html. But
>>> at the end of the LDIF data, I get a newline and a 'None', whereas
>>> there is no such thing in the result shown in that example. How to get
>>> rid of those unwanted characters. I am using Python-LDAP 2.3.5-1 on
>>> Debian Lenny.
>> Could you please post your code (in a short form) demonstrating the
>> issue? Note that there is a new-line after each entry record. But was
>> 'None' is in your case is not clear to me.
>>
> 
> Basically what I am trying to do with this code is that, I manipulate
> the result returned by ldapsearch to remove some attributes and
> generate a LDIF output for the modified entry.
> 
> <code>
>         res_type, result_data=l.result(res_id,0)
>         if (result_data==[]):
>             break
>         dn=result_data[0][0]
> 	resd=result_data[0][1]
>         resd["objectClass"].remove("inetLocalMailRecipient")
> 	    resd["objectClass"].remove("organizationalPerson")
> 	    resd["objectClass"].remove("inetOrgPerson")
>         resd["objectClass"].remove("posixAccount")
>         lw=ldif.LDIFWriter(sys.stdout)
> 	guru=lw.unparse(dn,resd)
> 	print guru
> </code>

Your code looks like processing of LDAP search results (because of the
res_type). I'd recommend to look at the actual data in dictionary resd.
Also note that the identiation seems wrong. This could be because of
cut&paste to your MUA from the editor with different tab-interpretation.
But make sure identiation is correct in the real code.

Ciao, Michael.

Re: LDIF Generation using Python-LDAP

[Guruprasad <lgp...@gm...>]

2009/5/16 Guruprasad <lgp...@gm...>:
> Hi,
>
> 2009/5/16 Michael Ströder <mi...@st...>:

> <code>
>        res_type, result_data=l.result(res_id,0)
>        if (result_data==[]):
>            break
>        dn=result_data[0][0]
>        resd=result_data[0][1]
>        resd["objectClass"].remove("inetLocalMailRecipient")
>            resd["objectClass"].remove("organizationalPerson")
>            resd["objectClass"].remove("inetOrgPerson")
>        resd["objectClass"].remove("posixAccount")
>        lw=ldif.LDIFWriter(sys.stdout)
>        guru=lw.unparse(dn,resd)
>        print guru
> </code>
>
> Is it some issue or am I making some mistakes with general usage of Python?
>
> Thank you.
>
> Regards,
> L.Guruprasad
>

My ldapsearch query returns only one record. I have written such a filter.

Regards,
Guruprasad

Re: LDIF Generation using Python-LDAP

[Guruprasad <lgp...@gm...>]

Hi,

2009/5/16 Michael Ströder <mi...@st...>:
> Guruprasad wrote:
>> Hi,
>> I tried generating a LDIF file from a dictionary using 'ldif' module
>> as illustrated in http://www.python-ldap.org/doc/html/ldif.html. But
>> at the end of the LDIF data, I get a newline and a 'None', whereas
>> there is no such thing in the result shown in that example. How to get
>> rid of those unwanted characters. I am using Python-LDAP 2.3.5-1 on
>> Debian Lenny.
>
> Could you please post your code (in a short form) demonstrating the
> issue? Note that there is a new-line after each entry record. But was
> 'None' is in your case is not clear to me.
>

Basically what I am trying to do with this code is that, I manipulate
the result returned by ldapsearch to remove some attributes and
generate a LDIF output for the modified entry.

<code>
        res_type, result_data=l.result(res_id,0)
        if (result_data==[]):
            break
        dn=result_data[0][0]
	resd=result_data[0][1]
        resd["objectClass"].remove("inetLocalMailRecipient")
	    resd["objectClass"].remove("organizationalPerson")
	    resd["objectClass"].remove("inetOrgPerson")
        resd["objectClass"].remove("posixAccount")
        lw=ldif.LDIFWriter(sys.stdout)
	guru=lw.unparse(dn,resd)
	print guru
</code>

Is it some issue or am I making some mistakes with general usage of Python?

Thank you.

Regards,
L.Guruprasad

Re: LDIF Generation using Python-LDAP

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

Guruprasad wrote:
> Hi,
> I tried generating a LDIF file from a dictionary using 'ldif' module
> as illustrated in http://www.python-ldap.org/doc/html/ldif.html. But
> at the end of the LDIF data, I get a newline and a 'None', whereas
> there is no such thing in the result shown in that example. How to get
> rid of those unwanted characters. I am using Python-LDAP 2.3.5-1 on
> Debian Lenny.

Could you please post your code (in a short form) demonstrating the
issue? Note that there is a new-line after each entry record. But was
'None' is in your case is not clear to me.

Ciao, Michael.

LDIF Generation using Python-LDAP

[Guruprasad <lgp...@gm...>]

Hi,
I tried generating a LDIF file from a dictionary using 'ldif' module
as illustrated in http://www.python-ldap.org/doc/html/ldif.html. But
at the end of the LDIF data, I get a newline and a 'None', whereas
there is no such thing in the result shown in that example. How to get
rid of those unwanted characters. I am using Python-LDAP 2.3.5-1 on
Debian Lenny.

Thank you.

Regards,
Guruprasad.

Re: Any example of Server/Client Side Sorting?

[Zhang H. <zhb...@gm...>]

Michael Ströder wrote:
> mycmp=lambda x,y: cmp(x[0].lower(), y[0].lower())
> alist.sort(mycmp)

I found this and solved too.
Big thanks :)


-- 
Best regards.

Zhang Huangbin

- Open Source Mail Server Solution for RHEL, CentOS, Debian:
  http://code.google.com/p/iredmail/

Re: Any example of Server/Client Side Sorting?

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

Zhang Huangbin wrote:
>  >>> cmp=lambda x,y: cmp(x[0].lower(), y[0].lower())
> 
>  >>> alist.sort(cmp)

Ouch! One should probably not mask the standard function name cmp.
So try this:

mycmp=lambda x,y: cmp(x[0].lower(), y[0].lower())
alist.sort(mycmp)

Ciao, Michael.

Re: Any example of Server/Client Side Sorting?

[Zhang H. <zhb...@gm...>]

Michael Ströder wrote:
>
> Sorry, there's a typo in there:
>
> cmp=lambda x,y: cmp(x[0].lower(), y[0}.lower())
>                                      ^
> Should be ]


I found that before, but got the same error:

 >>> alist
[('mail=postmaster@a.cn,o=domainAdmins,dc=iredmail,dc=org', {'mail': 
['postmaster@a.cn'], 'accountStatus': ['active'], 'enabledService': 
['awstats'], 'domainGlobalAdmin': ['yes']}), 
('mail=www@a.cn,o=domainAdmins,dc=iredmail,dc=org', {'mail': 
['www@a.cn'], 'accountStatus': ['active'], 'domainGlobalAdmin': 
['yes']}), ('mail=www5@a.cn,o=domainAdmins,dc=iredmail,dc=org', {'mail': 
['www5@a.cn'], 'accountStatus': ['active'], 'domainGlobalAdmin': 
['no']}), ('mail=www3@a.cn,o=domainAdmins,dc=iredmail,dc=org', {'mail': 
['www3@a.cn'], 'accountStatus': ['active'], 'domainGlobalAdmin': ['no']})]

 >>> cmp=lambda x,y: cmp(x[0].lower(), y[0].lower())

 >>> alist.sort(cmp)
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  ...... SKIP MANY LINES HERE ......
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
  File "<stdin>", line 1, in <lambda>
RuntimeError: maximum recursion depth exceeded

-- 
Best regards.

Zhang Huangbin

- Open Source Mail Server Solution for RHEL, CentOS, Debian:
  http://code.google.com/p/iredmail/

Re: Any example of Server/Client Side Sorting?

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

Zhang Huangbin wrote:
> Michael Ströder wrote:
>> Compare function for case-insensitive comparison of the DN:
>>
>> cmp=lambda x,y: cmp(x[0].lower(), y[0}.lower())
> 
> I tried this compare function, but got this err msg:

Sorry, there's a typo in there:

cmp=lambda x,y: cmp(x[0].lower(), y[0}.lower())
                                     ^
Should be ]

Ciao, Michael.

Re: Any example of Server/Client Side Sorting?

[Zhang H. <zhb...@gm...>]

Michael Ströder wrote:
>
> Compare function for case-insensitive comparison of the DN:
>
> cmp=lambda x,y: cmp(x[0].lower(), y[0}.lower())
>
>   

Thanks Michael. :)

I tried this compare function, but got this err msg:

----
RuntimeError: maximum recursion depth exceeded
----

The result contains less than 10 records.



-- 
Best regards.

Zhang Huangbin

- Open Source Mail Server Solution for RHEL, CentOS, Debian:
  http://code.google.com/p/iredmail/

Re: Any example of Server/Client Side Sorting?

[Russell J. <ra...@cs...>]

Michael Ströder wrote:
> Zhang Huangbin wrote:
>> Michael Ströder wrote:
>> Tring to learn ldap programing from web2ldap now. Thanks for your great
>> program. :)
> 
> Bear in mind that I started learning Python when the first code was
> written almost 11 years ago. So I have to admit that many parts are
> really ugly code and not really good programming examples.

Every programmer I've ever talked to always thinks their own code sucks.

-- 
Russell A. Jackson <ra...@cs...>
Network Analyst
California State University, Bakersfield

With a gentleman I try to be a gentleman and a half, and with a fraud I
try to be a fraud and a half.
		-- Otto von Bismarck