[python-ldap] Python3 Status Question

[Raphaël Barrois]

On Tue, 27 May 2014 17:41:24 -0400
David Stanek <dstanek at dstanek.com> wrote:

> On Tue, May 27, 2014 at 5:35 PM, Raphaël Barrois
> <raphael.barrois at m4x.org>wrote:
> 
> > On Tue, 27 May 2014 12:26:58 -0400
> > David Stanek <dstanek at dstanek.com> wrote:
> >
> > > Hello All,
> > >
> > > I'm in the process of getting the OpenStack Keystone project to
> > > work on Python 3. Part of this work is to get all of our
> > > dependencies to also work against Python 3. It looks like there
> > > have been several attempts for python-ldap, with the most
> > > promising being the one recently announced[1] on this list.
> > >
> > > This patchset is working so far, but I have quite a bit more
> > > testing to do including more changes to Keystone so that I can
> > > actually run full tests. What is the process for getting these
> > > patches accepted?
> > >
> > > Thanks!
> > >
> > > 1.
> > > https://mail.python.org/pipermail/python-ldap/2014q1/003348.html
> > >
> >
> 
> 
> > - Decide that switching to Python3 should be an occasion for
> >   significant API redesign, and release that version under a new
> > name
> 
> 
> I'm curious about this option. Is a API redesign on the table because
> of Py3 changes (str->bytes, etc.) or is it just an opportunity to
> make a change?
> 
> 
> 

This seemed to be an option when I scrubbed the archives before
starting my Py3 version, see for instance
https://mail.python.org/pipermail/python-ldap/2012q2/003115.html.

Regarding my Py3 fork, the goal is to provide a consistent API for both
Py2 and Py3, where code using python-ldap can be used the same in both
versions.
This is not always easy, especially in places where objects
are returned as bytes where the RFC states they are actually UTF-8
encoded text ; in such situations, we'll have to decide whether we go
for backwards-compatibility or for future-proof design.


-- 
Raphaël