Xapian devel - Aug 2004 - Required Python version?

I was filing some old mail and found this:

On Mon, Jun 23, 2003 at 03:07:12PM +0100, James Aylett
wrote:
> [R]eally we should be testing which version of Python we're compiling
> against ... pre-2.0 definitely won't work because the internal C API
> changed, and I suspect we may rely on 2.1 features in some way (__eq__
> vs. __cmp__ comes to mind).
Currently the configure test checks for Python 1.5 or newer (because
SWIG requires at least that).  Should this be changed to 2.0 or 2.1
or what?

Cheers,
    Olly

On Sat, Aug 21, 2004 at 02:44:15PM +0100, Olly Betts wrote:
> > [R]eally we should be testing which version of Python we're
compiling
> > against ... pre-2.0 definitely won't work because the internal C
API
> > changed, and I suspect we may rely on 2.1 features in some way (__eq__
> > vs. __cmp__ comes to mind).
> 
> Currently the configure test checks for Python 1.5 or newer (because
> SWIG requires at least that).  Should this be changed to 2.0 or 2.1
> or what?
2.0 as a minimum. I'm using __cmp__ / __eq__ tricks to get the
iterators to behave like Python iterators, so not all aspects will
work without 2.1; I'd be happy to require 2.1 though, because it's
been out for a long time, and 2.0 wasn't around for all that long as I
remember.

J

-- 
/--------------------------------------------------------------------------\
  James Aylett                                                  xapian.org
  james at tartarus.org                               uncertaintydivision.org