[python3-ldap] R: Library name change?

[Python3-ldap]

Hello Will,
when I started to develop python3-ldap I was focused on filling the gap for ldap in python3, so I named the library thinking it would be a python 3 only package. At first stage of development I saw it was quite easy to write code that worked either in python 3 and python 2, so I started to test against both version (actually 2.6, 2.7 and 3.x). I was surprised to find that people started using python3-ldap in python 2 too, despite the presence of the python-ldap package (with a completely different API). So the name change could reflect that. There is really a little portion of code specific to python 3 in the library and it requires python 3.4 to take advantage of the new SSLContext class of the SSL package.

So regarding your two questions I can say that (1) there is no python 3 "core" on the library, there are just a few 'if str == bytes:' statements to check if string is unicode or not (and a few backported functions regarding SSL) and that (2) the obvious way to maintain compatibility is to release two packages with different names (python3-ldap and python-ldap3) and the same content, but I don't think this is an acceptable solution Another less obvious way could be to make python3-ldap a "wrapper" to python-ldap3, this could leave space for an hypothetical python2-ldap that could be released when major differences arise.

Bye,
Giovanni

----- Messaggio originale -----
Da: "Will Yardley" <python.org at veggiechinese.net>
Inviato: ‎17/‎08/‎2014 01:13
A: "python3-ldap at python.org" <python3-ldap at python.org>
Oggetto: Re: [python3-ldap] Library name change?

On Sun, Aug 10, 2014 at 12:23:25AM +0200, python3ldap wrote:

> I've been asked to change the name of the library from python3-ldap to
> python-ldap3. This makes sense because the library is still agnostic about
> the Python interpreter and is strictly following version 3 of the
> LDAP protocol.

I have always thought the name doesn't sound right as-is, especially
since it has Python 2 compatibility. I think python-ldap3 makes a lot
more sense (though tying it into the version of the LDAP protocol,
rather than into the iteration of the python-ldap library, e.g.,
python-ldap2) potentially does make the name obsolete if there's ever a
new version of the LDAP protool (possibly unlikely at this point, I
guess).

A few thoughts, though:
1) I'm wondering if it's possible to make the library use native Python 3
libraries when available in the case where you've had to re-create
Python 3 functionality for compatibility with 2, and defining the things
that do need to be back-ported in as central a way as possible.

2) Given the complaint mentioned by another poster on this topic, is
there a way to make the module allow the old name to continue to work
for backwards compatibility?

w

_______________________________________________
python3-ldap mailing list
python3-ldap at python.org
https://mail.python.org/mailman/listinfo/python3-ldap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python3-ldap/attachments/20140817/8d5e915a/attachment.html>