[python3-ldap] Library name change?

[Gary Waters]

Why not just do an "import as"  ?

For example:

import NEW_MODULE_NAME as OLD_MODULE_NAME
or
import PYTHON_LDAP3 as LDAP3-PYTHON

So you can continue to use methods with the old name.

This would allow the name to evolve to something that is more logical,
and have little impact to previously written scripts.

Hope this helps,
Gary

On 08/16/2014 04:04 PM, Will Yardley wrote:
> 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
>