python-ldap-dev — discussion among developers

Re: Installation Problem

[Ben O. <zo...@th...>]

At 04:23 PM 1/2/02 -0500, you wrote:
>There are TWO commands.  The first starts "cvs -d... login", the second is 
>"cvs -d ... checkout"

Then what is the name of the module? Or, how do I ls to find out?
TIA
BenO

Re: Installation Problem

[Rich S. <rs...@zo...>]

There are TWO commands.  The first starts "cvs -d... login", the second 
is "cvs -d ... checkout"
	/r$

Zolera Systems, Your Key to Online Integrity
Securing Web services: XML, SOAP, Dig-sig, Encryption
http://www.zolera.com

Re: Installation Problem

[Ben O. <zo...@th...>]

At 04:09 PM 1/2/02 -0500, you wrote:
>>If not, if you would be so kind as to translate the following ...
>
>
>They are showing two UNIX-style command-line invocations of CVS.
>
>Type the first command to "login" to the remote site.  When it asks for a 
>password, just hit the RETURN key.

Cool. When I tried the first time it didn't work: now I see my error. Thus, 
the following:

#cvs 
-d:pserver:ano...@cv...:/cvsroot/python-ldap login
(Logging in to ano...@cv...)
CVS password:
#

Okay, what do I do at the last prompt?

>Type the second command to fetch the latest sources and make a local 
>mirror of the source tree.

So, in other words, I only need the command listed above (but again, what 
comes next?)

>Cute sitename.

Thanks!
BenO

Re: Installation Problem

[Rich S. <rs...@zo...>]

> If not, if you would be so kind as to translate the following ...


They are showing two UNIX-style command-line invocations of CVS.

Type the first command to "login" to the remote site.  When it asks for 
a password, just hit the RETURN key.

Type the second command to fetch the latest sources and make a local 
mirror of the source tree.

Hope this helps.  Cute sitename.
	/r$
-- 
Zolera Systems, Your Key to Online Integrity
Securing Web services: XML, SOAP, Dig-sig, Encryption
http://www.zolera.com

Re: Installation Problem

[Ben O. <zo...@th...>]

At 09:49 PM 1/2/02 +0100, you wrote:
>Ben Ocean wrote:
> >
> > I'm afraid I'm thoroughly confused now!
> > <disclaimer> This is my first time with CVS</disclaimer>
>
>Well, it seems you should use Joe's RPMs. He built them recently.

Fine, but will that default to all these flags?

#sh configure --with-ldap=/usr/local/openldap 
--with-ldap-lib=/usr/local/openldap/libraries 
--with-ldap-inc=/usr/local/openldap/include 
--with-python=/usr/local/bin/python --with-kerberos 
--with-kerberos-lib=/usr/krb5-1.2.2/src/lib

If not, if you would be so kind as to translate the following I would be 
much obliged:

This project's SourceForge CVS repository can be checked out through 
anonymous (pserver) CVS with the following instruction set. The module you 
wish to check out must be specified as the modulename. When prompted for a 
password for anonymous, simply press the Enter key.
cvs 
-d:pserver:ano...@cv...:/cvsroot/python-ldap 
login

cvs -z3 
-d:pserver:ano...@cv...:/cvsroot/python-ldap 
co modulename

At a command prompt I enter what? Or, is it in a browser address bar? What 
do I do?
TIA,
BenO

Re: Installation Problem

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

Ben Ocean wrote:
> 
> I'm afraid I'm thoroughly confused now!
> <disclaimer> This is my first time with CVS</disclaimer>

Well, it seems you should use Joe's RPMs. He built them recently.

Ciao, Michael.

Re: Installation Problem

[Ben O. <zo...@th...>]

At 09:03 PM 1/2/02 +0100, you wrote:
>You should follow the "Anonymous CVS instructions":

I'm afraid I'm thoroughly confused now!
<disclaimer> This is my first time with CVS</disclaimer>
I read the following:

This project's SourceForge CVS repository can be checked out through 
anonymous (pserver) CVS with the following instruction set. The module you 
wish to check out must be specified as the modulename. When prompted for a 
password for anonymous, simply press the Enter key.
cvs 
-d:pserver:ano...@cv...:/cvsroot/python-ldap 
login

cvs -z3 
-d:pserver:ano...@cv...:/cvsroot/python-ldap 
co modulename

So, what exactly do I do? At a command prompt I enter what? Or, is it in a 
browser address bar? What do I do?
TIA,
BenO

Re: Installation Problem

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

the cvs tar image is unusable since its CVS format..

just follow the instructions for doing a cs checkout. Or, grab my SRPM,
install it, and in /usr/src/redhat/SOURCES will be the
python-ldap-cvs-010102.tar.gz file for your enjoyment.

On 1/2/02 11:38 AM, "Ben Ocean" <zo...@th...> wrote:

> At 07:19 PM 1/2/02 +0100, you wrote:
>> Ben Ocean wrote:
>>> 
>>> Darn. I was afraid of that. Is there no bridge for python2x and openldap2x?
>> 
>> There is. Check out recent version from CVS.
> 
> Okay, I d'l'd, edited setup.cfg,v and ran make but it complained that it
> couldn't find setup.py so I moved setup.py,v to setup.py but that caused an
> error. This is my first time working with CVS: what am I doing wrong?
> TIA,
> BenO
> 
> P.S.
> Thanks to Joe Little for similar comments.
> Thanks to Jens Vagelpohl for recommending the FAQ.
> 
> 
> 
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: Installation Problem

[Ben O. <zo...@th...>]

At 07:19 PM 1/2/02 +0100, you wrote:
>Ben Ocean wrote:
> >
> > Darn. I was afraid of that. Is there no bridge for python2x and openldap2x?
>
>There is. Check out recent version from CVS.

Okay, I d'l'd, edited setup.cfg,v and ran make but it complained that it 
couldn't find setup.py so I moved setup.py,v to setup.py but that caused an 
error. This is my first time working with CVS: what am I doing wrong?
TIA,
BenO

P.S.
Thanks to Joe Little for similar comments.
Thanks to Jens Vagelpohl for recommending the FAQ.

Re: Installation Problem

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

Ben Ocean wrote:
> 
> Darn. I was afraid of that. Is there no bridge for python2x and openldap2x?

There is. Check out recent version from CVS.

But beware it *solely* works with OpenLDAP 2 libs which up to now
are not available on e.g. Win32. Win32 C compiler hackers jump on
in!

Ciao, Michael.

Re: Installation Problem

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

there is a FAQ on the python-ldap site (among other docs and searchable 
list archives):

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

jens


On Wednesday, January 2, 2002, at 01:14 , Ben Ocean wrote:

> At 06:58 PM 1/2/02 +0100, you wrote:
>> Ben Ocean wrote:
>> >
>> > make[1]: *** [constants.o] Error 1
>> > make[1]: Leaving directory `/usr/local/python-ldap-1.10alpha3/Modules'
>> > make: *** [_ldapmodule-build] Error 2
>>
>> Well, you snipped the compiler's error message.
>>
>> Which version of the OpenLDAP libs are you using?
>> python-ldap-1.10alpha3 can't be compiled against OpenLDAP 2.x.
>
> Darn. I was afraid of that. Is there no bridge for python2x and 
> openldap2x?
> TIA,
> BenO
>
>
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: Installation Problem

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

take the latest CVS snapshot or grab my RPMs.. they are designed for
OpenLDAP 2.x and do work with python 2.x (2.1 for the RPM)

On 1/2/02 10:14 AM, "Ben Ocean" <zo...@th...> wrote:

> At 06:58 PM 1/2/02 +0100, you wrote:
>> Ben Ocean wrote:
>>> 
>>> make[1]: *** [constants.o] Error 1
>>> make[1]: Leaving directory `/usr/local/python-ldap-1.10alpha3/Modules'
>>> make: *** [_ldapmodule-build] Error 2
>> 
>> Well, you snipped the compiler's error message.
>> 
>> Which version of the OpenLDAP libs are you using?
>> python-ldap-1.10alpha3 can't be compiled against OpenLDAP 2.x.
> 
> Darn. I was afraid of that. Is there no bridge for python2x and openldap2x?
> TIA,
> BenO
> 
> 
> 
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: Installation Problem

[Ben O. <zo...@th...>]

At 06:58 PM 1/2/02 +0100, you wrote:
>Ben Ocean wrote:
> >
> > make[1]: *** [constants.o] Error 1
> > make[1]: Leaving directory `/usr/local/python-ldap-1.10alpha3/Modules'
> > make: *** [_ldapmodule-build] Error 2
>
>Well, you snipped the compiler's error message.
>
>Which version of the OpenLDAP libs are you using?
>python-ldap-1.10alpha3 can't be compiled against OpenLDAP 2.x.

Darn. I was afraid of that. Is there no bridge for python2x and openldap2x?
TIA,
BenO

Re: Installation Problem

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

Ben Ocean wrote:
> 
> make[1]: *** [constants.o] Error 1
> make[1]: Leaving directory `/usr/local/python-ldap-1.10alpha3/Modules'
> make: *** [_ldapmodule-build] Error 2

Well, you snipped the compiler's error message.

Which version of the OpenLDAP libs are you using?
python-ldap-1.10alpha3 can't be compiled against OpenLDAP 2.x.

Ciao, Michael.

Installation Problem

[Ben O. <zo...@th...>]

Hi;
Got this on make:

make[1]: *** [constants.o] Error 1
make[1]: Leaving directory `/usr/local/python-ldap-1.10alpha3/Modules'
make: *** [_ldapmodule-build] Error 2

I've used every available flag in my config to try to eliminate any problems:

#sh configure --with-ldap=/usr/local/openldap 
--with-ldap-lib=/usr/local/openldap/libraries 
--with-ldap-inc=/usr/local/openldap/include 
--with-python=/usr/local/bin/python --with-kerberos 
--with-kerberos-lib=/usr/krb5-1.2.2/src/lib

What am I missing?
TIA,
BenO

Re: Building python-ldap RPMs (was: TLS context)

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

Joe Little wrote:
> 
> Did you just do a new commit on CVS?

Nope.

You might want to consider subscribing to list python-ldap-commits
to get notification about CVS commits (low-traffic).

  http://lists.sourceforge.net/lists/listinfo/python-ldap-commits

Ciao, Michael.

Re: Building python-ldap RPMs (was: TLS context)

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

Did you just do a new commit on CVS?

the -O1 and -O2 both created .pyo files only.. no .pyc files (odd, that).

Anywho.. I've generated release 2, which drops the .pyo files and does the
post-install compile all, though it feels somewhat wrong since I may be
affecting other things on the system. Furthermore, I don't get the free
chksums on the .pyo and .pyc files.. Oh well, it definitely makes the build
process easier.

-2 is up there, and it does dump the compileall output to the screen. Once
we move beyond the cvs phase, I'll /dev/null that output since it will make
for ugly installations


On 1/1/02 7:29 PM, "Michael Str=F6der" <mi...@st...> wrote:

> Joe,
>=20
> better you test the current CVS version and my recently sent diffs.
> IMHO we can think about packaging later...
>=20
> Joe Little wrote:
>>=20
>>>> This is all changed behaviour so to speak with distutils.
>>>=20
>>> Was byte-compiling enabled in your RPM before? How?
>>=20
>> I did a "make install" into a $DESTDIR (build root) --- make install did
>> everything correctly in the GNU configure days. setup.py is a bit too sm=
art
>> :)
>=20
> You should definitely avoid using make install. The Makefile was
> produced by David who cannot stay away from typing make. Buuuh! But
> as an OpenBSD hacker he does not spend much time with thinking about
> RPMs... ;-)
>=20
>>> What's wrong with using python setup.py bdist_rpm ? BTW: It contains
>>> byte-compiled *.pyc files in my case (tested right now).
>>=20
>> It fails for me since it finds python is 1.5
>=20
> You simply have to type (assuming you used make altinstall when
> installing the Python 2.1 version):
> $ python2.1 setup.py bdist_rpm
>=20
>> (which doesn't include distutils)
>=20
> BTW: There are DistUtils for Python 1.5.
>=20
>> Second, it looks like the current
>> cvs snapshots enforce a 2.0.0pre1 version string.
>=20
> Well, this can be easily solved...
>=20
>>> When installing from source distribution (packaged with python
>>> setup.py sdist) this will do the trick:
>>> $ python setup.py install -O1
>>> $ python setup.py install -O2
>>=20
>> what do -01 and -02 do.. or is that O1 O2 (letter 'O')?
>=20
> -O1 -> *.pyc
> -O2 -> *.pyo
>=20
>>> You could also write a small post-install script using
>>> compileall.py.
>=20
> And how about this as post-install script?
>=20
> $ python2.1 /usr/lib/python2.1/compileall.py
> $ python2.1 -O /usr/lib/python2.1/compileall.py
>=20
> Ciao, Michael.
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Building python-ldap RPMs (was: TLS context)

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

Joe,

better you test the current CVS version and my recently sent diffs.
IMHO we can think about packaging later...

Joe Little wrote:
> 
> >> This is all changed behaviour so to speak with distutils.
> >
> > Was byte-compiling enabled in your RPM before? How?
> 
> I did a "make install" into a $DESTDIR (build root) --- make install did
> everything correctly in the GNU configure days. setup.py is a bit too smart
> :)

You should definitely avoid using make install. The Makefile was
produced by David who cannot stay away from typing make. Buuuh! But
as an OpenBSD hacker he does not spend much time with thinking about
RPMs... ;-)

> > What's wrong with using python setup.py bdist_rpm ? BTW: It contains
> > byte-compiled *.pyc files in my case (tested right now).
> 
> It fails for me since it finds python is 1.5

You simply have to type (assuming you used make altinstall when
installing the Python 2.1 version):
$ python2.1 setup.py bdist_rpm

> (which doesn't include distutils)

BTW: There are DistUtils for Python 1.5.

> Second, it looks like the current
> cvs snapshots enforce a 2.0.0pre1 version string.

Well, this can be easily solved...

> > When installing from source distribution (packaged with python
> > setup.py sdist) this will do the trick:
> > $ python setup.py install -O1
> > $ python setup.py install -O2
> 
> what do -01 and -02 do.. or is that O1 O2 (letter 'O')?

-O1 -> *.pyc
-O2 -> *.pyo

> > You could also write a small post-install script using
> > compileall.py.

And how about this as post-install script?

$ python2.1 /usr/lib/python2.1/compileall.py
$ python2.1 -O /usr/lib/python2.1/compileall.py

Ciao, Michael.

Re: TLS context

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

ok.. answers below.

On 1/1/02 6:59 PM, "Michael Str=F6der" <mi...@st...> wrote:

> Joe Little wrote:
>>=20
>> first, another error. It looks like Lib/ldap.py is not found and a warni=
ng
>> is thrown.
>=20
> Module ldap was turned in a module package. See Lib/ldap/.
>=20
>> The generated files are handled differently by setup.py, and I
>> get a different file list. Also, a noticed a version string of
>> python-ldap-2.0.0pre1.. should I use this instead of naming it
>> "python-ldap-cvs-pythonv"
>=20
> Use a timestamp until a (pre-)release is done.
>=20
>> Here is the file list (/usr/share/doc excepted):
>>=20
>> /usr/lib/python2.1/site-packages ....
>>=20
>> _ldap.so
>> ldapurl.py
>> ldif.py
>> ldap/__init__.py
>> ldap/async.py
>> ldap/functions.py
>> ldap/ldapobject.py
>> ldap/modlist.py
>=20
> Nothing wrong with that.
>=20
>> There used to be an ldap.pth generated
>=20
> Pre-DistUtils days, was never available on Win32 anyway.
>=20
>> and other such, and it definitely include an ldap.py before.
>=20
> See ldap/__init__.py.
>=20
>> It also does not pre-compile any .py file.
>=20
> Can I pass DistUtils an option to enable byte-compiling before
> packaging?
>=20

Can't seem to find any

>> This is all changed behaviour so to speak with distutils.
>=20
> Was byte-compiling enabled in your RPM before? How?

I did a "make install" into a $DESTDIR (build root) --- make install did
everything correctly in the GNU configure days. setup.py is a bit too smart
:)

>=20
>> I cannot perform a
>> "install" since it will only generate onto the real directories and not =
an
>> alternative build root.
>=20
> What's wrong with using python setup.py bdist_rpm ? BTW: It contains
> byte-compiled *.pyc files in my case (tested right now).
>=20

It fails for me since it finds python is 1.5 (which doesn't include
distutils). Even changing the env to /usr/bin/python2 causes things to
progress and then die out later when it goes into "Python-LDAP-2.0.0pre1"
and runs setup.py again and can't import distutils (its running python1.5
again). There should be a way to handle this without env variables, since I
want to be as deterministic as possible. Second, it looks like the current
cvs snapshots enforce a 2.0.0pre1 version string. I'd need to diff away fro=
m
that but then I couldn't use bdist_rpm (you can't use it within another
RPM... :) )

>> Checking a real install, the only thing lacking is
>> the precompile of .py files, and I believe that is not necessary.
>=20
> When installing from source distribution (packaged with python
> setup.py sdist) this will do the trick:
> $ python setup.py install -O1
> $ python setup.py install -O2

what do -01 and -02 do.. or is that O1 O2 (letter 'O')? Again, this sounds
like it invokes actions on its discovered install dirs (/usr/lib instead of
/var/tmp/%var/usr/lib). Please tell me I'm wrong :)

>=20
> You could also write a small post-install script using
> compileall.py.
>=20
> Ciao, Michael.

Re: Stripped LDAPObject.c

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

Michael Ströder wrote:
> 
> Michael Ströder wrote:
> >
> > I've stripped all *_doc strings and almost all *_s() methods from
> > LDAPObject.c. Also removed the deprecated Kerberos stuff completely.
> 
> Since I now hopefully solved all the backwards compability issues
> with ldapobject.py I'd like to check in the radically stripped
> Modules/LDAPObject.c.
> 
> Any objections against that?

Hmm, no response so far. Please test the attached gzipped diff.

Ciao, Michael.

Re: TLS context

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

Joe Little wrote:
> 
> first, another error. It looks like Lib/ldap.py is not found and a warning
> is thrown.

Module ldap was turned in a module package. See Lib/ldap/.

> The generated files are handled differently by setup.py, and I
> get a different file list. Also, a noticed a version string of
> python-ldap-2.0.0pre1.. should I use this instead of naming it
> "python-ldap-cvs-pythonv"

Use a timestamp until a (pre-)release is done.

> Here is the file list (/usr/share/doc excepted):
> 
> /usr/lib/python2.1/site-packages ....
> 
> _ldap.so
> ldapurl.py
> ldif.py
> ldap/__init__.py
> ldap/async.py
> ldap/functions.py
> ldap/ldapobject.py
> ldap/modlist.py

Nothing wrong with that.

> There used to be an ldap.pth generated

Pre-DistUtils days, was never available on Win32 anyway.

> and other such, and it definitely include an ldap.py before.

See ldap/__init__.py.

> It also does not pre-compile any .py file.

Can I pass DistUtils an option to enable byte-compiling before
packaging?

> This is all changed behaviour so to speak with distutils.

Was byte-compiling enabled in your RPM before? How?

> I cannot perform a
> "install" since it will only generate onto the real directories and not an
> alternative build root.

What's wrong with using python setup.py bdist_rpm ? BTW: It contains
byte-compiled *.pyc files in my case (tested right now).

> Checking a real install, the only thing lacking is
> the precompile of .py files, and I believe that is not necessary.

When installing from source distribution (packaged with python
setup.py sdist) this will do the trick:
$ python setup.py install -O1
$ python setup.py install -O2

You could also write a small post-install script using
compileall.py.

Ciao, Michael.

beta release of new CVS-built RPMS

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

Ok.. in case people want to see where I'm at on this or want to use the
cvs-build of python-ldap, I've placed a first release of my RPMs on
www.open-it.org (files) as well as ftp.open-it.org in /pub/redhat7.2

They expect a RH7.2 system, as well as python 2.x (2.1 specifically).

I've also placed a rebuild of redhat-rawhide OpenLDAP 2.0.19 RPMs there.
SRPMS are heading up there now.

Version names and content inside RPMs may change as I fix problems. Hope
this is useful and brings new year cheer to the group :)

Re: TLS context

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

on the subject of python versions.. I dropped my added string, and will rel=
y
on RPM to do the right thing most of the time. This _could_ break for
python2.2 users, but the naming just was getting too weird. Tell me if I
should keep the version string in there. It actually had to be like
"python-ldap-python2.1-cvs-1.i386.rpm" or -2.0.0pre1-1.i386.rpm...


On 1/1/02 6:34 PM, "Joe Little" <jl...@op...> wrote:

> Ok.. almost done here.
>=20
> first, another error. It looks like Lib/ldap.py is not found and a warnin=
g
> is thrown. The generated files are handled differently by setup.py, and I
> get a different file list. Also, a noticed a version string of
> python-ldap-2.0.0pre1.. should I use this instead of naming it
> "python-ldap-cvs-pythonv" where pythonv is the pythonv compiled with (I
> demand at least 2.x, but people may be using 2.1 or 2.2, and site-package=
s
> are different)???
>=20
> Here is the file list (/usr/share/doc excepted):
>=20
> /usr/lib/python2.1/site-packages ....
>=20
> _ldap.so
> ldapurl.py
> ldif.py
> ldap/__init__.py
> ldap/async.py
> ldap/functions.py
> ldap/ldapobject.py
> ldap/modlist.py
>=20
> There used to be an ldap.pth generated and other such, and it definitely
> include an ldap.py before. It also does not pre-compile any .py file. Thi=
s
> is all changed behaviour so to speak with distutils. I cannot perform a
> "install" since it will only generate onto the real directories and not a=
n
> alternative build root. Checking a real install, the only thing lacking i=
s
> the precompile of .py files, and I believe that is not necessary.
>=20
> Tell me if the above list of files is insufficient.
>=20
> On 1/1/02 5:57 PM, "Michael Str=F6der" <mi...@st...> wrote:
>=20
>> Joe Little wrote:
>>>=20
>>> On 1/1/02 5:31 PM, "Michael Str=F6der" <mi...@st...> wrote:
>>>=20
>>>> You probably have to upgrade your OpenLDAP 2 libs. (That's what I
>>>> had to do.)
>>>>=20
>>> Damnit.. your right. I did my build on a virgin redhat 7.2 box with inc=
luded
>>> OpenLDAP 2.0.11 and not my version of the packages. Treats me right. a =
beta
>>> OpenLDAP 2.0.19 RPM sailed right through. Does anyone know where this i=
s
>>> fixed so that I can log it?
>>=20
>> Hmm, looking into the OpenLDAP libs directory:
>>=20
>> liblber.so.2.0.13
>> libldap.so.2.0.13
>>=20
>> 2.0.13?!?
>>=20
>> Ciao, Michael.
>>=20
>> _______________________________________________
>> Python-LDAP-dev mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>=20
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: TLS context

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

Ok.. almost done here.

first, another error. It looks like Lib/ldap.py is not found and a warning
is thrown. The generated files are handled differently by setup.py, and I
get a different file list. Also, a noticed a version string of
python-ldap-2.0.0pre1.. should I use this instead of naming it
"python-ldap-cvs-pythonv" where pythonv is the pythonv compiled with (I
demand at least 2.x, but people may be using 2.1 or 2.2, and site-packages
are different)???

Here is the file list (/usr/share/doc excepted):

/usr/lib/python2.1/site-packages ....

_ldap.so
ldapurl.py
ldif.py
ldap/__init__.py
ldap/async.py
ldap/functions.py
ldap/ldapobject.py
ldap/modlist.py

There used to be an ldap.pth generated and other such, and it definitely
include an ldap.py before. It also does not pre-compile any .py file. This
is all changed behaviour so to speak with distutils. I cannot perform a
"install" since it will only generate onto the real directories and not an
alternative build root. Checking a real install, the only thing lacking is
the precompile of .py files, and I believe that is not necessary.

Tell me if the above list of files is insufficient.

On 1/1/02 5:57 PM, "Michael Str=F6der" <mi...@st...> wrote:

> Joe Little wrote:
>>=20
>> On 1/1/02 5:31 PM, "Michael Str=F6der" <mi...@st...> wrote:
>>=20
>>> You probably have to upgrade your OpenLDAP 2 libs. (That's what I
>>> had to do.)
>>>=20
>> Damnit.. your right. I did my build on a virgin redhat 7.2 box with incl=
uded
>> OpenLDAP 2.0.11 and not my version of the packages. Treats me right. a b=
eta
>> OpenLDAP 2.0.19 RPM sailed right through. Does anyone know where this is
>> fixed so that I can log it?
>=20
> Hmm, looking into the OpenLDAP libs directory:
>=20
> liblber.so.2.0.13
> libldap.so.2.0.13
>=20
> 2.0.13?!?
>=20
> Ciao, Michael.
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: TLS context

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

Joe Little wrote:
> 
> On 1/1/02 5:31 PM, "Michael Ströder" <mi...@st...> wrote:
> 
> > You probably have to upgrade your OpenLDAP 2 libs. (That's what I
> > had to do.)
> >
> Damnit.. your right. I did my build on a virgin redhat 7.2 box with included
> OpenLDAP 2.0.11 and not my version of the packages. Treats me right. a beta
> OpenLDAP 2.0.19 RPM sailed right through. Does anyone know where this is
> fixed so that I can log it?

Hmm, looking into the OpenLDAP libs directory:

liblber.so.2.0.13
libldap.so.2.0.13

2.0.13?!?

Ciao, Michael.