python-ldap-dev — discussion among developers

Re: Preparing release 2.3.1

[Torsten K. <pyt...@tk...>]

Hi Michael,
> I'd like to release 2.3.1 soon.
still one question: Do you plan to upload some .eggs to PyPI then?
I meanwhile successfully build eggs for i686-linux as well as Mac OS X 10.4 PPC (Intel platforms should work the same way) using Py 2.3 + 2.4.

Nice to have would be an egg for the Windows platform, which I can't build due to the lack of a proper Windows devel environment.

Anyway, after 2.3.1 is released, I'd be happy to contribute the mentioned .egg files - could you then upload them to PyPI?
I could do that, too, but it's for you to decide...

Best regards,
Torsten
-- 
Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de

Ich schreibe dir einen langen Brief, weil ich keine Zeit habe,
einen kurzen zu schreiben.    -- Johann Wolfgang von Goethe --

Re: [PATCH] RFC 3876 control (return values filter)

[Andreas H. <aha...@te...>]

On Monday 16 July 2007 07:50:30 Michael Str=F6der wrote:
> Andreas Hasenack wrote:
> > On Thu, May 31, 2007 at 07:23:36PM -0300, Andreas Hasenack wrote:
> >> I will still see about the decode part and then post what I have.
> >
> > Attached is my current patch. Keep in mind I did this basically using
> > the current code as a template.
>
> I've committed this patch to CVS. I'd appreciate if you could also
> provide a small script for Demo/.

Thanks, I'll get you such a script soon.

Preparing release 2.3.1

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

HI!

I'd like to release 2.3.1 soon. There are some interesting improvements
in HEAD but not yet released. Therefore testing of HEAD is needed.
Thanks to the contributors!

Please provide feedback ideally on the mailing list. Thanks.

Ciao, Michael.

Current CHANGES:

Released 2.3.1 2007-07-xx

Changes since 2.3.0:

* Support for setuptools (building .egg, thanks to Torsten)
* Support for matched values control (RFC 3876, thanks to Andreas)

Lib/
* Fixed ldif (see SF#1709111, thanks to Dmitry)

Modules/
* Added constant MOD_INCREMENT to support
  modify+increment extension (see RFC 4525, thanks to Andreas)

Re: [PATCH] RFC 3876 control (return values filter)

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

Andreas Hasenack wrote:
> On Thu, May 31, 2007 at 07:23:36PM -0300, Andreas Hasenack wrote:
>> I will still see about the decode part and then post what I have.
> 
> Attached is my current patch. Keep in mind I did this basically using
> the current code as a template.

I've committed this patch to CVS. I'd appreciate if you could also
provide a small script for Demo/.

Ciao, Michael.

Re: python-ldap on PyPI (next version)

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

Hi Torsten,

thanks for improving setup.py.

Torsten Kurbad wrote:
> 
> after a few modifications, the patch keeps full backward compatibility
> to distutils and (hopefully at least ;o) works with Python 2.2 and
> Windows.

I've tested it (under openSUSE Linux) without setuptools with 2.2 and
2.5 and it works. So I've committed it to CVS.

Ciao, Michael.

Re[3]: python-ldap on PyPI (next version)

[Torsten K. <pyt...@tk...>]

Hi folks, greetings Michael,

after a few modifications, the patch keeps full backward compatibility
to distutils and (hopefully at least ;o) works with Python 2.2 and
Windows.

Major changes:

* fallback to distutils.core, if setuptools are not available
* all additional keyword arguments to setup() are set on condition that
  setuptools could be imported
* got rid completely of the packages= and platform= keywords (packages
  doesn't work, after all - and doesn't seem to be necessary)

Would be glad, if someone could try out the whole thing for Win32,
Python 2.2, with and without setuptools, etc.

Have a nice sunday!
Torsten
-- 
Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de

Never make anything simple and efficient when a way can be found to
make it complex and wonderful.              - Murphy's Law No. 13 -

Re[2]: python-ldap on PyPI

[Torsten K. <pyt...@tk...>]

On Saturday, July 14, 2007 at 16:47 Michael Str=F6der wrote:
>> Using a standard Linux distribution, like Gentoo,
> Hmm, all modifications to setup.py should work on Windows either.

Do you mean _native_ Win32 or rather Cygwin? Is there native OpenLDAP
support for Win32?

>> 1. If not already done so, follow the instructions at
>> http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-inst=
all

> Is it a MUST?
For the .egg, yes, since only setuptools provide the necessary bdist_egg co=
mmand.

>> -from distutils.core import setup, Extension
>> +from setuptools import setup, Extension, find_packages

> Hmm, this replaces distutils completely. Isn't there any pattern for a
> fall-back to distutils if setuptools is not available?

Oh, something like:

setuptools =3D False
try:
    from setuptools import setup, Extension, find_packages
    setuptools =3D True
except:
    from distutils.core import setup, Extension

and later on:

packages =3D None
if setuptools and float(sys.version[:3]) < 2.3:
    packages =3D find_packages('ldap', 'ldap.schema')

>> +if float(sys.version[:3]) < 2.3:
>> +    packages =3D find_packages('ldap', 'ldap.schema')
>> [..]
>>       #-- Python packages (doesn't work with Python prior 2.3)
>> -#    packages =3D ['ldap', 'ldap.schema'],
>> +        packages =3D packages,

> And how to build that with Python 2.2 and earlier?
Oh, the comment:
  #-- Python packages (doesn't work with Python prior 2.3)
is not mine. Thus, I set packages to None above the if-statement
(which should actually be the same as leaving the packages variable
out completely, which was the case in the original setup.py).

>> +        platforms =3D ['posix']

> Shouldn't that be derived from sys.platform during build?
> Or at least to be defined in setup.cfg. That's what it's for.

Sorry, I didn't know that - this was my first platform-specific egg, so
I thought it's to be set there (I found this one in another setup.py).

> For now I consider your patch to solve the .egg thingy for you. I won't
> patch the general setup.py in standard source distribution. I might add
> your version of setup.py as setup_egg.py under Build/ in the source
> distribution.

Hmm, perhaps we could come to a more general solution cooperatively.
PyPI is quickly becoming for Python what CPAN is for Perl, so I don't
think that an important package like Python-LDAP should stand back there.

On monday I'll try to create a setup.py that still works with distutils
and Python 2.2. But due to my lack of experience in Windows programming
I'd highly appreciate, if you (or someone else with the necessary
experience) could test the whole thing on the Win32 platform...

Do we have a deal? ;o)

Greetings
Torsten
--=20
Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de

Never make anything simple and efficient when a way can be found to
make it complex and wonderful.              - Murphy's Law No. 13 -

Re: python-ldap on PyPI

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

Torsten Kurbad wrote:
> 
> I just created a first .egg of python-ldap.

Thanks for contributing this.

> Using a standard Linux distribution, like Gentoo,

Hmm, all modifications to setup.py should work on Windows either.

> 1. If not already done so, follow the instructions at
> http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install

Is it a MUST?

> -from distutils.core import setup, Extension
> +from setuptools import setup, Extension, find_packages

Hmm, this replaces distutils completely. Isn't there any pattern for a
fall-back to distutils if setuptools is not available?

> +if float(sys.version[:3]) < 2.3:
> +    packages = find_packages('ldap', 'ldap.schema')
> [..]
>  	#-- Python packages (doesn't work with Python prior 2.3)
> -#	packages = ['ldap', 'ldap.schema'],
> +        packages = packages,

And how to build that with Python 2.2 and earlier?

> +        platforms = ['posix']

Shouldn't that be derived from sys.platform during build?
Or at least to be defined in setup.cfg. That's what it's for.

For now I consider your patch to solve the .egg thingy for you. I won't
patch the general setup.py in standard source distribution. I might add
your version of setup.py as setup_egg.py under Build/ in the source
distribution.

Ciao, Michael.

Re: python-ldap on PyPI

[Torsten K. <pyt...@tk...>]

Hi folks,

I just created a first .egg of python-ldap.
Using a standard Linux distribution, like Gentoo, this can easily be
replayed:

0. Make sure that you have a recent version of openldap, openssl and
cyrus-sasl libraries and headers installed.

1. If not already done so, follow the instructions at
http://peak.telecommunity.com/DevCenter/EasyInstall#installing-easy-install

2. Download and unpack the latest python-ldap tarball (2.3)

3. cd into python-ldap-2.3 and apply the attached (and hopefully
unmangled) patch as follows
patch -p1 <path/to/python-ldap-2.3-setuptools.diff

4. Run
python setup.py bdist_egg

5. If everything went well, you'll have a python-ldap-egg in the newly
created subfolder dist, e.g.
python_ldap-2.3-py2.4-linux-i686.egg

If things don't work or you are too lazy to try these steps, you may
test my precompiled egg at
http://svn.kmrc.de/download/distribution/python_ldap-2.3-py2.4-linux-i686.egg

It is linked against
- openssl 0.9.8e
- cyrus-sasl-2.1.22
- openldap-2.3.35
- glibc-2.5

Any feedback is highly appriciated!

Best regards,
Torsten
-- 
Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de

Ich schreibe dir einen langen Brief, weil ich keine Zeit habe,
einen kurzen zu schreiben.    -- Johann Wolfgang von Goethe --

Re: python-ldap on PyPI

[Timur I. <Tim...@oi...>]

Torsten Kurbad wrote:
> Timur Izhbulatov wrote:
>> Hi guys,
>>
>> Any progress with python-ldap.egg? If nobody's working on this I'll
>> have to make it myself because I need it too.
>>
>> Cheers,
> Hi Timur,
> 
> yes, me and my colleagues will prepare sth. during the next couple of
> days. My boss already has some experience with eggs, so he will provide
> some counseling... ;o)

Sounds good. Good luck! :)

Cheers,
-- 
Timur Izhbulatov
OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia
P:+7 495 105 7245 + ext.205 F:+7 495 105 7246 E:Tim...@oi...
Building Successful Supply Chains - One Solution At A Time.
www.oilspace.com

Re: python-ldap on PyPI

[Timur I. <Tim...@oi...>]

Michael Ströder wrote:
> Torsten Kurbad wrote:
>> I'm currently involved in a project, using Zope3, there we would need a
>> proper python-ldap.egg from the Python Cheeseshop. I realized that
>> someone checked in some specs there
>> (http://www.python.org/pypi/python-ldap/2.0.11), but there's no .egg
>> file attached to this record - therefore my project fails to build.
>>
>> So my question is twofold:
>> a) Who maintains the PyPI entries of python-ldap? Is it actively
>> maintained in general?
>> b) If not, how can I help to get it done?
> 
> Since I never looked into .egg files I'd appreciate if you could provide
> one and I do the rest of putting it on PyPI.

Hi guys,

Any progress with python-ldap.egg? If nobody's working on this I'll have to 
make it myself because I need it too.

Cheers,
-- 
Timur Izhbulatov
OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia
P:+7 495 105 7245 + ext.205 F:+7 495 105 7246 E:Tim...@oi...
Building Successful Supply Chains - One Solution At A Time.
www.oilspace.com

Re: python-ldap on PyPI

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

Torsten Kurbad wrote:
> 
> I'm currently involved in a project, using Zope3, there we would need a
> proper python-ldap.egg from the Python Cheeseshop. I realized that
> someone checked in some specs there
> (http://www.python.org/pypi/python-ldap/2.0.11), but there's no .egg
> file attached to this record - therefore my project fails to build.
> 
> So my question is twofold:
> a) Who maintains the PyPI entries of python-ldap? Is it actively
> maintained in general?
> b) If not, how can I help to get it done?

Since I never looked into .egg files I'd appreciate if you could provide
one and I do the rest of putting it on PyPI.

Ciao, Michael.

python-ldap on PyPI

[Torsten K. <pyt...@tk...>]

Hi there,

I'm currently involved in a project, using Zope3, there we would need a
proper python-ldap.egg from the Python Cheeseshop. I realized that
someone checked in some specs there
(http://www.python.org/pypi/python-ldap/2.0.11), but there's no .egg
file attached to this record - therefore my project fails to build.

So my question is twofold:
a) Who maintains the PyPI entries of python-ldap? Is it actively
maintained in general?
b) If not, how can I help to get it done?

Best regards,
Torsten

Re: subtree move

[Roland H. <rol...@ad...>]

Michael Ströder wrote:

> Hmm, glancing over the code I'd suggest to implement it separately. I'd
> try to rename the whole sub-tree first and then handle
> ldap.NOT_ALLOWED_ON_NONLEAF smoothly.

That was my intention.

-- Roland

Re: subtree move

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

Roland Hedberg wrote:
>> I have something slightly more efficient based on evaluating
>> hasSubordinates or similar attributes for sub-tree deletion in web2ldap.
> 
> If you are willing to share I'd love to have it :-)

Hmm, look into web2ldap's source (GPL): function DelTree() in
pylib/w2lapp/delete.py.

But it's not in a shape to directly use it. It's more munged into the
application. And the hasSubordinates handling is slightly different from
what you need. It rather trys to delete a whole entry and retries
differently after receiving ldap.NOT_ALLOWED_ON_NONLEAF.

Hmm, glancing over the code I'd suggest to implement it separately. I'd
try to rename the whole sub-tree first and then handle
ldap.NOT_ALLOWED_ON_NONLEAF smoothly.

Ciao, Michael.

Re: subtree move

[Roland H. <rol...@ad...>]

Michael Ströder wrote:
> Roland Hedberg wrote:

>> So, has anyone implemented modifyDN on top of python-ldap ?
> 
> Or are you talking about moving sub-trees in case the LDAP server does
> not support sub-tree renaming?

Yes, I can make no assumptions as to what the server can or can't.

> I have something slightly more efficient based on evaluating
> hasSubordinates or similar attributes for sub-tree deletion in web2ldap.

If you are willing to share I'd love to have it :-)

-- Roland

Re: subtree move

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

Roland Hedberg wrote:
> 
> It seems like Python-ldap does not support modifyDN. That is moving a
> subtree from one place on a server to another place on the same server.

See methods rename() and rename_s() with argument newsuperior. You can
rename a sub-tree with e.g. with OpenLDAP/back-hdb.

> So, has anyone implemented modifyDN on top of python-ldap ?
> 
> I realize it will not be very efficient, but then the subtree I might
> have to move is only one level deep and with a limited set of entries.

Or are you talking about moving sub-trees in case the LDAP server does
not support sub-tree renaming?

I have something slightly more efficient based on evaluating
hasSubordinates or similar attributes for sub-tree deletion in web2ldap.

Ciao, Michael.

subtree move

[Roland H. <rol...@ad...>]

Hi!

It seems like Python-ldap does not support modifyDN. That is moving a
subtree from one place on a server to another place on the same server.

So, has anyone implemented modifyDN on top of python-ldap ?

I realize it will not be very efficient, but then the subtree I might
have to move is only one level deep and with a limited set of entries.

-- Roland

Re: Experiments with pyasn1 and preread control

[Andreas H. <aha...@te...>]

On Wed, Jun 06, 2007 at 02:16:11PM +0200, Michael Ströder wrote:
> Andreas,
> 
> Andreas Hasenack wrote:
> > I have been having fun with controls. Today I tried to use the Pre-Read
> > control together with the modify+increment extension, so that
> > modify+increment becomes actually useful.
> 
> Thanks for sharing your experiences.
> 
> > I first added the encoding part to the ldap.so module, but later got a
> > response from the pyasn1 mailing list and tried again in pure python.
> 
> Saw your postings there. I'm also lurking on the pyasn1-users mailing
> list. The author seems to be quite responsive.
> 
> 
> > The decoding part will probably be more difficult... As the control
> > response is a SearchResultEntry which is a bit more complex to decode.
> 
> How about exposing the function LDAPmessage_to_python() in message.c.
> It's used also to parse search results invoked by l_ldap_result3() in
> LDAPObject.c.

Hmm, the problem is that at that moment of decoding the control I don't
have access to the LDAP* structure anymore, so I can't use
LDAPmessage_to_python(). Or I'm missing something.

All I have is the controlValue, which is an ldap message as returned by
ldap_result which I would usually parse with ldap_first_message(3) and
ldap_next_message(3).

CfP period for LDAPcon 2007 extended

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

HI!

again I would like to make readers of this list aware of LDAPcon 2007.
Please see https://www.guug.de/veranstaltungen/ldapcon2007/index.html
for details.

The deadline for the CfP was extended to 2007-06-30. See
https://www.guug.de/veranstaltungen/ldapcon2007/cfp.html for details if
you'd like to submit a proposal for a presentation.

Looking forward to meet you there.

Ciao, Michael.

Re: [PATCH] RFC 3876 control (return values filter)

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

Andreas Hasenack wrote:
> On Fri, Jun 01, 2007 at 11:27:45AM -0300, Andreas Hasenack wrote:
>> On Thu, May 31, 2007 at 07:23:36PM -0300, Andreas Hasenack wrote:
>>> I will still see about the decode part and then post what I have.
>> Attached is my current patch. Keep in mind I did this basically using
>> the current code as a template.
>>
>> I ended up not implementing the decode part, I'm not sure for what it
>> would be needed. Just for completeness?
> 
> No comments? Because of the missing decode part?

Sorry, it's on my to-do list. Glancing over it I have no objections
against the patch. I will try to commit it next week.

Ciao, Michael.

Re: [PATCH] RFC 3876 control (return values filter)

[Andreas H. <aha...@te...>]

On Fri, Jun 01, 2007 at 11:27:45AM -0300, Andreas Hasenack wrote:
> On Thu, May 31, 2007 at 07:23:36PM -0300, Andreas Hasenack wrote:
> > I will still see about the decode part and then post what I have.
> 
> Attached is my current patch. Keep in mind I did this basically using
> the current code as a template.
> 
> I ended up not implementing the decode part, I'm not sure for what it
> would be needed. Just for completeness?

No comments? Because of the missing decode part?

[Fwd: Re: python-ldap for Python 2.5 on Windows?]

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

HI!

Grabbed this posting from the Python newsgroup.
I did not test this build yet and I don't know which features it supports.

Ciao, Michael.

-------- Original Message --------
Subject: Re: python-ldap for Python 2.5 on Windows?
Date: Fri, 08 Jun 2007 10:23:09 -0700
From: Waldemar Osuch <wal...@gm...>
Organization: http://groups.google.com
Newsgroups: comp.lang.python
References: <mai...@py...>

On Jun 8, 6:36 am, Benedict Verheyen <benedict.verhe...@gmail.com>
wrote:
> Hi,
>
> i found python-ldap for version Python 2.4.
> Is there i place i can find a version for 2.5?
>
> If not, how can i build it myself for Windows?
>

I have managed to build it for myself using MinGW:
http://www.osuch.org-a.googlepages.com/python-ldap-2.3.win32-py2.5.exe

See if it will work for you

Waldemar

Re: Experiments with pyasn1 and preread control

[Andreas H. <aha...@te...>]

On Wed, Jun 06, 2007 at 02:16:11PM +0200, Michael Ströder wrote:
> Andreas,
> 
> Andreas Hasenack wrote:
> > I have been having fun with controls. Today I tried to use the Pre-Read
> > control together with the modify+increment extension, so that
> > modify+increment becomes actually useful.
> 
> Thanks for sharing your experiences.
> 
> > I first added the encoding part to the ldap.so module, but later got a
> > response from the pyasn1 mailing list and tried again in pure python.
> 
> Saw your postings there. I'm also lurking on the pyasn1-users mailing
> list. The author seems to be quite responsive.
 
Yes he does

> > The decoding part will probably be more difficult... As the control
> > response is a SearchResultEntry which is a bit more complex to decode.
> 
> How about exposing the function LDAPmessage_to_python() in message.c.
> It's used also to parse search results invoked by l_ldap_result3() in
> LDAPObject.c.

Right. Later on I was thinking "but wait, python-ldap must already have
such a function". I will check.

Thanks

Re: Experiments with pyasn1 and preread control

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

Andreas,

Andreas Hasenack wrote:
> I have been having fun with controls. Today I tried to use the Pre-Read
> control together with the modify+increment extension, so that
> modify+increment becomes actually useful.

Thanks for sharing your experiences.

> I first added the encoding part to the ldap.so module, but later got a
> response from the pyasn1 mailing list and tried again in pure python.

Saw your postings there. I'm also lurking on the pyasn1-users mailing
list. The author seems to be quite responsive.


> The decoding part will probably be more difficult... As the control
> response is a SearchResultEntry which is a bit more complex to decode.

How about exposing the function LDAPmessage_to_python() in message.c.
It's used also to parse search results invoked by l_ldap_result3() in
LDAPObject.c.

Ciao, Michael.