[python3-ldap] python3-ldap 0.9.5.4 released

[python3ldap]

Hi Will,
you're right, I chose those configuration parameter at the very
beginning of the project, when I started reading the different RFCs.
So they made sense because I could refer to the relevant part of the
RFC, and it was not clear to me what and how many parameters I needed.
I will make them simpler in a next release, maintaining compatability
with the older for a while.

Thanks for the suggestion.
Bye,
Giovanni

2014-09-23 20:12 GMT+02:00 Will Yardley <python.org at veggiechinese.net>:
> On Tue, Sep 23, 2014 at 07:33:52PM +0200, python3ldap wrote:
>
>> Do you think that something is still missing?
>
> I wonder if there's a terser or easier to read way of doing this:
>
> from ldap3 import [...] SEARCH_SCOPE_WHOLE_SUBTREE
> c.search('o=test','(objectClass=*)', SEARCH_SCOPE_WHOLE_SUBTREE, [...]
>
> At the least, the long constant, while precise, takes up an awful lot of
> real estate.
>
> I'm not sure what the cleanest / most proper / most "pythonic" way would
> be, but I would have thought just having a parameter specified like
> 'scope=subtree' or something (with a default that represents the most
> common use-case) would be simpler and much easier to read, unless this
> way of doing things is deprecated for some reason.
>
> w
>
> _______________________________________________
> python3-ldap mailing list
> python3-ldap at python.org
> https://mail.python.org/mailman/listinfo/python3-ldap