[Xapian-tickets] [Xapian] #346: Python 3 support

[Xapian]

#346: Python 3 support
-----------------------------+----------------------------------------------
 Reporter:  olly             |       Owner:  richard  
     Type:  defect           |      Status:  new      
 Priority:  high             |   Milestone:  1.1.2    
Component:  Xapian-bindings  |     Version:  SVN trunk
 Severity:  normal           |    Keywords:           
Blockedby:                   |    Platform:  All      
 Blocking:                   |  
-----------------------------+----------------------------------------------

Old description:

> In ["ToDoFor1.1.0"], Richard wrote:
> > Support for python 3.  May already work, but needs testing, and may
> > need some tweaking.  Could do with someone going through all the
> > places where strings are supplied and returned, and deciding
> > whether the API should expect byte strings or unicode strings (or
> > both).
>
> Assigning to you, since you added it to the list and I don't really know
> what to look for...

New description:

 This is what I'm aware of that still needs to be done:

     * Unicode handling needs sorting out properly and not just by
 commenting out testcases which detect the current problems! I think
 Richard has some ideas.

     * I get lots of warnings like:

 {{{
 xapian/__init__.py:4221: DeprecationWarning: object.__new__() takes no
 parameters
 }}}

 ----

 In ["ToDoFor1.1.0"], Richard wrote:
 > Support for python 3.  May already work, but needs testing, and may
 > need some tweaking.  Could do with someone going through all the
 > places where strings are supplied and returned, and deciding
 > whether the API should expect byte strings or unicode strings (or
 > both).

 Assigning to you, since you added it to the list and I don't really know
 what to look for...

--

Comment(by olly):

 OK, I've incorporated the {{{__len__}}} change and sorted out the
 {{{__next__}}} changes so that they don't break Python 2 support but still
 work with Python 3.

 I've updated the description with the remaining two items, and pruned the
 patch again.

 Richard seemed to have some ideas on IRC for sorting out the Unicode
 stuff, and I've no idea about the {{{__new__}}} stuff, so I'm not planning
 to work on this further for now, so feel free to.

-- 
Ticket URL: <http://trac.xapian.org/ticket/346#comment:12>
Xapian <http://xapian.org/>
Xapian