python-ldap-dev — discussion among developers

Re: (no subject)

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

Gabby James wrote:
> 
> If I start python2.2 while I am a user (gabby) in the 
> /home/gabby/python-ldap-2.0.0pre14 directory, everything works fine.  If 
> I am in any other directory and start python2.2, I receive errors:
> [..]
> Traceback (most recent call last):
>  File "<stdin>", line 1, in ?
> AttributeError: 'module' object has no attribute 'open'

Are you sure you're using the very same Python interpreter all the time?

Find out with 'which' command.

Ciao, Michael-

Re: (no subject)

[Jean J. <je...@up...>]

> If I start python2.2 while I am a user (gabby) in the 
> /home/gabby/python-ldap-2.0.0pre14 directory, everything works fine.

If you do that, you import the ldap *class*.

> If I am in any other directory and start python2.2, 

If you do that, you import the ldap *module*. In order to import the
class, you need to do: `from ldap import ldap`.

-- 
Jean Jordaan
http://www.upfrontsystems.co.za

Re: (no subject)

[Gabby J. <liz...@ho...>]

I do have one more question for you all.

If I start python2.2 while I am a user (gabby) in the 
/home/gabby/python-ldap-2.0.0pre14 directory, everything works fine.  If I 
am in any other directory and start python2.2, I receive errors:

[gabby@xdx-dhcp-x-xxx-x gabby]$ python2.2
Python 2.2.2 (#1, Feb 24 2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>import ldap
>>>ldap.open("discovery.colostate.edu")
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
AttributeError: 'module' object has no attribute 'open'

The ldap server I am using I found on a list of public servers on the 
internet.

_________________________________________________________________
Enjoy MSN 8 patented spam control and more with MSN 8 Dial-up Internet 
Service.  Try it FREE for one month!   http://join.msn.com/?page=dept/dialup

Re: (no subject)

[Joao S. O. B. <gw...@mp...>]

Hi there!

I just went through it (the ldap_first_reference error). It seens like=20
a mandatory first step for Python Ldapers.  :-)

I think I can figure out what is missing on your procedures:
Did you perform a clean-up of th e compiled files between the changes=20
on setup.cfg?

The error is in ldap_r, so you must put just ldap for linking, or fix=20
ldap_r yourself, according to the message I linked to in my earlier=20
e-mail today:
libs =3D ldap lber resolv

And them
python setup.py clean --all
python setup.py build
su
python setup.py install.

I am  rolling now.=20



On Tuesday 14 October 2003 1:38 pm, Gabby James wrote:
> I apologize for sending another help request on the infamous
> ldap_first_reference error but I just can't seem to figure it out
> even after reading old postings.
>
> I am using a RedHat 9.0 system with openldap-2.0.27-8 and
> python-2.2.2-26. I
> downloaded python-ldap-2.0.0pre14 and compiled.  When I start
> python and try an
> "import ldap" statement, I get the following error message:
>
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/lib/python2.2/site-packages/ldap/__init__.py", line
> 21, in ? from _ldap import *
> ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined
> symbol: ldap_first_reference
>
> I modified setup.cfg to try all of the following after reading old
> postings: libs =3D ldap_r lber sasl2 ssl crypto
> libs =3D ldap lber
> libs =3D ldap lber resolv
> libs =3D ldap_r lber
> libs =3D ldap_r ldap
>
> I compile python-ldap specifically with the version of python I am
> interested in:
> python2.2 setup.py build
> python2.2 setup.py install
>
> I have also seen the following comment "This is likely due to
> missing references.c and references.lo in
> libraries/libldap_r/Makefile.in".  I didn't try this 'casue I
> couldn't find the
> file on my system.  Could someone explain this in more detail?
>
> Any other thoughs on what is going wrong?
>
> Thank you.
> G.J.
>
> _________________________________________________________________
> Page a contact=92s mobile phone with  MSN Messenger 6.0. Download it
> now FREE! http://msnmessenger-download.com
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

=2D

Re: (no subject)

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

Gabby James wrote:
> ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined 
> symbol: ldap_first_reference

What does /usr/lib/python2.2/site-packages/_ldap.so say?

Ciao, Michael.

RE : (no subject)

[jean-marc p. <jea...@ac...>]

Install also openldap  openldap-stable-20030709.tgz.

Jean-Marc


-----Message d'origine-----
De : pyt...@li...
[mailto:pyt...@li...] De la part de Gabby
James
Envoy=E9 : mardi 14 octobre 2003 15:38
=C0 : pyt...@li...
Objet : (no subject)


I apologize for sending another help request on the infamous=20
ldap_first_reference error but I just can't seem to figure it out even
after=20
reading old postings.

I am using a RedHat 9.0 system with openldap-2.0.27-8 and
python-2.2.2-26. =20
I
downloaded python-ldap-2.0.0pre14 and compiled.  When I start python and
try=20
an
"import ldap" statement, I get the following error message:

Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.2/site-packages/ldap/__init__.py", line 21, in
?
    from _ldap import *
ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined
symbol:=20
ldap_first_reference

I modified setup.cfg to try all of the following after reading old
postings: libs =3D ldap_r lber sasl2 ssl crypto libs =3D ldap lber libs =
=3D
ldap lber resolv libs =3D ldap_r lber libs =3D ldap_r ldap

I compile python-ldap specifically with the version of python I am=20
interested in:
python2.2 setup.py build
python2.2 setup.py install

I have also seen the following comment "This is likely due to missing=20
references.c and references.lo in libraries/libldap_r/Makefile.in".  I
didn't try this 'casue I couldn't find=20
the
file on my system.  Could someone explain this in more detail?

Any other thoughs on what is going wrong?

Thank you.
G.J.

_________________________________________________________________
Page a contact=92s mobile phone with  MSN Messenger 6.0. Download it now
FREE!=20
   http://msnmessenger-download.com



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects. See the people
who have HELPED US provide better services: Click here:
http://sourceforge.net/supporters.php
_______________________________________________
Python-LDAP-dev mailing list Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

(no subject)

[Gabby J. <liz...@ho...>]

I apologize for sending another help request on the infamous 
ldap_first_reference error but I just can't seem to figure it out even after 
reading old postings.

I am using a RedHat 9.0 system with openldap-2.0.27-8 and python-2.2.2-26.  
I
downloaded python-ldap-2.0.0pre14 and compiled.  When I start python and try 
an
"import ldap" statement, I get the following error message:

Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.2/site-packages/ldap/__init__.py", line 21, in ?
    from _ldap import *
ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined symbol: 
ldap_first_reference

I modified setup.cfg to try all of the following after reading old postings:
libs = ldap_r lber sasl2 ssl crypto
libs = ldap lber
libs = ldap lber resolv
libs = ldap_r lber
libs = ldap_r ldap

I compile python-ldap specifically with the version of python I am 
interested in:
python2.2 setup.py build
python2.2 setup.py install

I have also seen the following comment "This is likely due to missing 
references.c and references.lo in
libraries/libldap_r/Makefile.in".  I didn't try this 'casue I couldn't find 
the
file on my system.  Could someone explain this in more detail?

Any other thoughs on what is going wrong?

Thank you.
G.J.

_________________________________________________________________
Page a contact’s mobile phone with  MSN Messenger 6.0. Download it now FREE! 
   http://msnmessenger-download.com

RE : Problem getting started to python ldap + redhat 9

[jean-marc p. <jea...@ac...>]

It works now for me on redhat 9, using pre14 and libs =3D lber ldap =
resolv
 in setup.cfg.=20


Jean-Marc






-----Message d'origine-----
De : pyt...@li...
[mailto:pyt...@li...] De la part de
Michael Str=F6der
Envoy=E9 : lundi 13 octobre 2003 18:27
=C0 : Joao S. O. Bueno
Cc : pyt...@li...
Objet : Re: Problem getting started to python ldap.


Joao S. O. Bueno wrote:
> ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined
> symbol: ldap_first_reference

There's probably something wrong with your local installation. Check
items=20
10. and 11. on

   http://python-ldap.sf.net/faq.shtml

> Or maybe, "import ldap" just is not the way to get started

It's definitely the way to get started.

$ python -c "import ldap;print ldap.__version__"
2.0.0pre14

> O yes...my contractors will absolutely disallow me to run unstable
> software there. So, how satble is "pre14",

I'm using it in several projects.

> and is there a release date set to 2.0?

No.

> Or, if there are some features waiting to be
> finished, what is the latest stable release?

Look into TODO what is still missing. Contributions welcome.

Ciao, Michael.



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects. See the people
who have HELPED US provide better services: Click here:
http://sourceforge.net/supporters.php
_______________________________________________
Python-LDAP-dev mailing list Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: Problem getting started to python ldap.

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

Joao S. O. Bueno wrote:
> ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined 
> symbol: ldap_first_reference

There's probably something wrong with your local installation. Check items 
10. and 11. on

   http://python-ldap.sf.net/faq.shtml

> Or maybe, "import ldap" just is not the way to get started

It's definitely the way to get started.

$ python -c "import ldap;print ldap.__version__"
2.0.0pre14

> O yes...my contractors will absolutely disallow me to run unstable 
> software there. So, how satble is "pre14",

I'm using it in several projects.

> and is there a release date set to 2.0?

No.

> Or, if there are some features waiting to be 
> finished, what is the latest stable release?

Look into TODO what is still missing. Contributions welcome.

Ciao, Michael.

Re: Problem getting started to python ldap.

[Joao S. O. B. <gw...@mp...>]

Hi...

I just figured it out - nothing like starting the ldap server first. 
:-)- Sorry if it was offtopic.

I still need someone to reply me on the stability issues tough.


Regards,
        JS
        -><-


On Monday 13 October 2003 11:28 am, Joao S. O. Bueno wrote:
> Hi there,
>
> I am new to LDAP, and will be developing some scripts to it.
>
>(...)
>
> O yes...my contractors will absolutely disallow me to run unstable
> software there. So, how satble is "pre14", and is there a release
> date set to 2.0? Or, if there are some features waiting to be
> finished, what is the latest stable release?
>
>
> Regards,
>
>       JS
>       -><-
>
>
>

Problem getting started to python ldap.

[Joao S. O. B. <gw...@mp...>]

Hi there,

I am new to LDAP, and will be developing some scripts to it.

I downloaded Python LDAP pre-14 for Linux. (here is mandrake 9.1), 
with default options. When I try to">>> import ldap", I get this:

>>> import ldap
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.2/site-packages/ldap/__init__.py", line 21, 
in ?
    from _ldap import *
ImportError: /usr/lib/python2.2/site-packages/_ldap.so: undefined 
symbol: ldap_first_reference
___
I just guess I am missing some library, and setup failed to point so. 
Could some one tell what is needed to run it?
Or maybe, "import ldap" just is not the way to get started - I usually 
import a module in an interactve python shell and read the online 
doc. to get started.

Any hints will be appreciated.

__

O yes...my contractors will absolutely disallow me to run unstable 
software there. So, how satble is "pre14", and is there a release 
date set to 2.0? Or, if there are some features waiting to be 
finished, what is the latest stable release?


Regards,

	JS
	-><-

python-ldap-2.0.0pre14 port to OpenBSD

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

The OpenBSD port of the python-ldap module has been updated to version 2.0.0pre14 of python-ldap.  The port can be downloaded at http://www.etc.msys.ch/ports/.

What is new:

- Support for python-ldap-2.0.0pre14
- Support for Python2.1 and Python2.2 (the port builds two binary packages by default)
- Slightly changed names for the binary packages

- mb

RE : Segmention fault on redhat 9 on ldap_simple_bind_s

[jean-marc p. <jea...@ac...>]

Thanks for yours previous answers, it works on debian,xp  without any
problem but on redhat 9 no.

What I can see using strace is
connect(4, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("X.X.X.X")}, 28) = 0
send(4, "]\242\1\0\0\1\0\0\0\0\0\0\00212\00261\003168\003192\7i"..., 44,
0) = 44
gettimeofday({1065437510, 248252}, NULL) = 0
poll([{fd=4, events=POLLIN, revents=POLLIN}], 1, 5000) = 1
ioctl(4, FIONREAD, [436])               = 0
recvfrom(4, "]\242\205\200\0\1\0\1\0\t\0\t\00212\00261\003168\00319"...,
1024, 0, {sa_family=AF_INET, sin_port=htons(53
), sin_addr=inet_addr("X.X.X.X")}, [16]) = 436
close(4)                                = 0
brk(0)                                  = 0x81d1000
brk(0x81d5000)                          = 0x81d5000
brk(0)                                  = 0x81d5000
brk(0x81d6000)                          = 0x81d6000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++



Any ideas ?

Thanks .

Re: ANN: python-ldap-2.0.0pre14

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

Marc Balmer wrote:
> 
> In TODO you mention that you should "Define common license for all
> modules".  Have you considere putting everything under the very liberal
> and very free BSD license?  That would make the software as free as it
> can bee (more free than GPL).

It's definitely not GPL'ed. My aim is to have a Python style license as 
already stated on the project's summary page. The intention is that you can 
do with python-ldap whatever you are allowed to do with Python itself. Does 
that suit your needs?

> Then, do you consider adding kerberosV support (which is in OpenLDAP)?

Not myself. There is some SASL support for Kerberos.

> If you don't, would you accept a patch if we didi it?

I'm not a C programmer therefore I prefer to keep myself away from sources 
under Modules/. I'd accept a patch provided that you are willing to maintain 
that part in the future (the next ~2 years).

Ciao, Michael.

Re: ANN: python-ldap-2.0.0pre14

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

On Fri, 03 Oct 2003 14:58:43 +0200
Michael Str=F6der <mi...@st...> wrote:

> Find a new pre-release of python-ldap:

Thanks for letting us know.  The OpenBSD port will be updated this weekend.

In TODO you mention that you should "Define common license for all modules"=
.  Have you considere putting everything under the very liberal and very fr=
ee BSD license?  That would make the software as free as it can bee (more f=
ree than GPL).

Then, do you consider adding kerberosV support (which is in OpenLDAP)?  If =
you don't, would you accept a patch if we didi it?

Regards from Switzerland,
Marc

ANN: python-ldap-2.0.0pre14

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

Find a new pre-release of python-ldap:

   http://python-ldap.sourceforge.net/

python-ldap provides an object-oriented API to access LDAP directory
servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for
that purpose. Additionally it contains modules for other LDAP-related
stuff (e.g. processing LDIF, LDAPURLs and LDAPv3 schema).

----------------------------------------------------------------
Released 2.0.0pre14 2003-10-03

Changes since 2.0.0pre13:

setup.py:
* Some modifications to ease building for Win32
* Added directory Build/ mainly intended for platform-specific
   examples of setup.cfg
* Fixed installing ldap.filter

ldap.ldapobject:
* Added class attribute LDAPObject.network_timeout mapped to
   set_option(ldap.OPT_NETWORK_TIMEOUT,..)
* LDAPObject.search_ext(): Pass arguments serverctrls,clientctrls
   to _ldap.search_ext()

ldap.sasl:
* Added class ldap.sasl.external for handling
   the SASL mechanism EXTERNAL
* Dictionary ldap.sasl.saslmech_handler_class built during import
   for all the known SASL mechanisms derived from class definitions

ldap.schema:
* More graceful handling of KeyError in SubSchema.attribute_types()
* New method SubSchema.get_inheritedattr() for retrieving inherited
   class attributes
* New method SubSchema.get_inheritedobj() for retrieving a
   schema element instance including all inherited class attributes

Re: Ldap.initialize vs. ldap.open [was: Re: Segmention fault on redhat 9 on ldap_simple_bind_s]

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

Mauro Cicognini wrote:
> Michael Str=F6der wrote:
>=20
>> Mauro Cicognini wrote:
>>
>>> May I say that I don't really care for ldap.initialize()? I must have=
=20
>>> missed something, but I really can't understand why the older style=20
>>> should be deprecated. What's the real win over using ldap.open()? :-\=

>>
>> ldaps:// and ldapi://
>=20
> You mean there's no way to open a secure LDAP connection other than=20
> using initialize()?

To use LDAP over SSL on a separate server port you need ldap.initialize()=
=2E
Using StartTLS extended operation is a different story.

Anyway use ldap.initialize() when developing apps to be more flexible in =
the
long run.

> Anyway, thanks for the explanation.
>=20
> BTW, what's "ldapi://"?

LDAP over Unix domain socket, no TCP (supported by OpenLDAP).

Ciao, Michael.

Re: Ldap.initialize vs. ldap.open [was: Re: Segmention fault on redhat 9 on ldap_simple_bind_s]

[Mauro C. <mci...@si...>]

Michael Str=F6der wrote:

> Mauro Cicognini wrote:
>
>> Jens Vagelpohl wrote:
>>
>>> ldap.open is deprecated. Read the docs and use ldap.initialize instea=
d.
>>
>>
>> May I say that I don't really care for ldap.initialize()? I must have =

>> missed something, but I really can't understand why the older style=20
>> should be deprecated. What's the real win over using ldap.open()? :-\
>
> ldaps:// and ldapi://

You mean there's no way to open a secure LDAP connection other than=20
using initialize()? Duh...

Anyway, thanks for the explanation.

BTW, what's "ldapi://"?

Mauro

Re: Ldap.initialize vs. ldap.open [was: Re: Segmention fault on redhat 9 on ldap_simple_bind_s]

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

Mauro Cicognini wrote:
> Jens Vagelpohl wrote:
> 
>> ldap.open is deprecated. Read the docs and use ldap.initialize instead.
> 
> May I say that I don't really care for ldap.initialize()? I must have 
> missed something, but I really can't understand why the older style 
> should be deprecated. What's the real win over using ldap.open()? :-\

ldaps:// and ldapi://

Ciao, Michael.

Ldap.initialize vs. ldap.open [was: Re: Segmention fault on redhat 9 on ldap_simple_bind_s]

[Mauro C. <mci...@si...>]

Jens Vagelpohl wrote:

> ldap.open is deprecated. Read the docs and use ldap.initialize instead.=


May I say that I don't really care for ldap.initialize()? I must have=20
missed something, but I really can't understand why the older style=20
should be deprecated. What's the real win over using ldap.open()? :-\

To put it in other words, I can't get myself to appreciate LDAP URLs,=20
which I find quite cumbersome & complicated. I can never remember=20
whether the "sub" argument goes before or after the attribute list, and=20
the inability to specify arguments by name (=E0 la Python) is to me a big=
=20
loss. Besides, I am instanciating an LDAP object, so it should be quite=20
clear I need an object which talks LDAP, without having to write it=20
again in a function argument :-)

IMHO, the LDAP URL only interesting usage is in a browser URL line (in=20
fact I strongly suspect is *was* invented for exactly that reason by=20
Netscape).

Anyway, there must be some reason, since ldap.open is being deprecated:=20
anyone caring to tell me why?

Thanks in advance,
Mauro

Re: Segmention fault on redhat 9 on ldap_simple_bind_s

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

> 	After read  mails from  archives, I sucessfully install
> python-ldap on redhat 9. (install tgz of openldap-2.1.22
> Modify source with  python-ldap_libs.patch ( -libs = ldap_r lber sasl2
> ssl crypto
> +libs = ldap_r ldap lber sasl2 ssl crypto ) before that I have an error
> messages on import undefined
>  symbol: ldap_first_reference)

A guy here at work replaced "ldap_r" with "ldap" in the LIBS line and 
it worked. He traced it to a broken Makefile in OpenLDAP itself (even 
in the latest RPMs) that did not mention all the right things (don't 
have the details here).


> Now I have a segmentation fault on simple bind
>>>> import ldap
>>>> l = ldap.open('ip_address')
>>>> l.simple_bind_s('','')
> Erreur de segmentation

ldap.open is deprecated. Read the docs and use ldap.initialize instead. 
Michael has produced wonderful python-style documentation, see 
python-ldap.sourceforge.net.


> I try to install the package on a debian and I have
>
>  python setup.py build
> Traceback (most recent call last):
>   File "setup.py", line 10, in ?
>     from distutils.core import setup, Extension
> ImportError: No module named distutils.core

I don't do Debian. I bet Debian's python package might be split up in 
all kinds of pieces and you need to install more of them. They're weird 
that way.

jens

Re: Segmention fault on redhat 9 on ldap_simple_bind_s

[<bjo...@it...>]

jean-marc pouchoulon:
> Helo ,
> 	After read  mails from  archives, I sucessfully install
> python-ldap on redhat 9. (install tgz of openldap-2.1.22
> Modify source with  python-ldap_libs.patch ( -libs =3D ldap_r lber sasl=
2
> ssl crypto
> +libs =3D ldap_r ldap lber sasl2 ssl crypto ) before that I have an err=
or
> messages on import undefined=20
>  symbol: ldap_first_reference)
> Now I have a segmentation fault on simple bind
> >>> import ldap
> >>> l =3D ldap.open('ip_address')
> >>> l.simple_bind_s('','')
> Erreur de segmentation
>=20
> I install the package on an xp system and it works perfectly.
>=20
> I try to install the package on a debian and I have=20
>=20
>  python setup.py build
> Traceback (most recent call last):
>   File "setup.py", line 10, in ?
>     from distutils.core import setup, Extension
> ImportError: No module named distutils.core
>=20
>=20
> Any help would be greatly appreciated, especially on RedHat.=20

For ldap:
install apt for redhat and use e.g. the following in your
/etc/apt/sources.list :
rpm http://apt.freshrpms.net redhat/9.0/en/i386 os updates freshrpms
rpm ftp://apt-rpm.tuxfamily.org/apt redhat/9.0/en/i386 os updates extra

(just sed'ed s/"7.3"/"9.0"/g, so I don't know if the url is correct.)

then, for both redhat and debian, run the following commands:
$ apt-get update && apt-get upgrade
$ apt-get install python-ldap

that's it.

--=20
Regards

Bj=F8rn Ove Gr=F8tan

Segmention fault on redhat 9 on ldap_simple_bind_s

[jean-marc p. <jea...@ac...>]

Helo ,
	After read  mails from  archives, I sucessfully install
python-ldap on redhat 9. (install tgz of openldap-2.1.22
Modify source with  python-ldap_libs.patch ( -libs = ldap_r lber sasl2
ssl crypto
+libs = ldap_r ldap lber sasl2 ssl crypto ) before that I have an error
messages on import undefined 
 symbol: ldap_first_reference)
Now I have a segmentation fault on simple bind
>>> import ldap
>>> l = ldap.open('ip_address')
>>> l.simple_bind_s('','')
Erreur de segmentation

I install the package on an xp system and it works perfectly.

I try to install the package on a debian and I have 

 python setup.py build
Traceback (most recent call last):
  File "setup.py", line 10, in ?
    from distutils.core import setup, Extension
ImportError: No module named distutils.core


Any help would be greatly appreciated, especially on RedHat. 
	

Jean-Marc Pouchoulon

Re: Too many results for this query...

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

Patrick Gelin wrote:
> 
> I would like to go through all LDAP users to register them into my Plone
> site (I need to use localroles and it's possible only after a Plone
> registration...)
 > [..]
> getUserNames: Cannot find any users (Too many results for this query)

This is a matter of the server-side configuration. Check size limits with 
the LDAP server's admin. Some LDAP server products allow setting 
user-specific limits.

> Is there a solution to grow the size of result accepted by python-ldap ?

Nope.

Ciao, Michael.

Too many results for this query...

[Patrick G. <pat...@rp...>]

Hi,

I would like to go through all LDAP users to register them into my Plone
site (I need to use localroles and it's possible only after a Plone
registration...)

So, I'm writing a python script (may be I have to write an external
method) which use the LDAPUserFolder::getUserNames API, and I've got the
error message below:

getUserNames: Cannot find any users (Too many results for this query)

Is there a solution to grow the size of result accepted by python-ldap ?
Is there an other solution ?

Thanks.

Patrick Gelin