[Xapian-tickets] [Xapian] #346: Python 3 support
Xapian
nobody at xapian.org
Fri Oct 4 01:37:02 BST 2013
#346: Python 3 support
--------------------------------------+------------------------------
Reporter: olly | Owner: richard
Type: defect | Status: assigned
Priority: highest | Milestone: 1.3.2
Component: Xapian-bindings (Python) | Version: SVN trunk
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: | Operating System: All
--------------------------------------+------------------------------
\
\
\
\
\
\
Old 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...
New description:
This is what I'm aware of that still needs to be done:
As of r17524, the python3 tests all pass (but we've disabled
"postingsource" under threads because it segfaults for currently unknown
reasons - all the testcases are run without threads and pass, and then
again with threads and we get this failure).
* Reject str from unserialise methods
* Return str for {{{version_string()}}}
* Check and update examples
* Check and update docs
* Resolve why postingsource testcase segfaults under threads
----
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):
Implemented {{{xapian.__version__}}} (for 2 and 3) in r17521, and
documented 3.2 as the minimum supported version in r17522.
Updated the todo list in the description.
\
\
\
--
Ticket URL: <http://trac.xapian.org/ticket/346#comment:68>
Xapian <http://xapian.org/>
Xapian
More information about the Xapian-tickets
mailing list