[RFC] Switch on tdb2 API by default?

[Jelmer Vernooij]

On Thu, Sep 29, 2011 at 07:52:48AM -0700, Kai Blin wrote:
> On 2011-09-29 02:40, Dan Shearer wrote:
> It gets a bit more complicated than that, though.

> > The Python team says "Python runs everywhere". That's their goal. So it
> > makes sense to me to push autoconf maintenance on weird/horrible
> > platforms off to the Python team.

> The Python team did end-of-life python2, though, and Samba doesn't work
> with python3. This causes all sorts of pain on ArchLinux already, where
> they are bleeding edge enough to make "python" point to python3 and
> break our build system.
... and going against the recommendations of Python upstream, which
recommends shipping python 3.0 as "python3" and python 2.x as "python"
even now that Python 3.X is out.

python 2.x does what we do; upstream probably won't
do any more feature work on it, but we can expect important bugs to be fixed
for quite some time. I don't see any reason to switch to Python 3 at this
point, and make life harder on the large number of platforms that
don't ship python3.

Cheers,

Jelmer