[
https://issues.apache.org/jira/browse/ZOOKEEPER-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TuxRacer updated ZOOKEEPER-877:
-------------------------------
Attachment: zookeeper.c.patch.v1
zookeeper.c
tests_py3k.tgz
Please find my first attempt to resolve this issue as three attachments
The zookeeper.c file (full code attached + diff file) now supports a
compilation with python3.1 and python2.6.
(I used conditional compilation as recommended at
http://docs.python.org/py3k/howto/cporting.html )
I converted the python test to py3k syntax using the '2to3' tool.
So we probably need to add a 2nd directory in the tree (and call it maybe
'tests_py3k'?)
good news:
all the test pass
bad news:
I could not make logging work (so had to comment the log setup in the tests)
Please let me know what you think, thanks. TuX
> zkpython does not work with python3.1
> -------------------------------------
>
> Key: ZOOKEEPER-877
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-877
> Project: Zookeeper
> Issue Type: Bug
> Components: contrib-bindings
> Affects Versions: 3.3.1
> Environment: linux+python3.1
> Reporter: TuxRacer
> Fix For: 3.4.0
>
> Attachments: tests_py3k.tgz, zookeeper.c, zookeeper.c.patch.v1
>
>
> as written in the contrib/zkpython/README file:
> "Python >= 2.6 is required. We have tested against 2.6. We have not tested
> against 3.x."
> this is probably more a 'new feature' request than a bug; anyway compiling
> the pythn module and calling it returns an error at load time:
> python3.1
> Python 3.1.2 (r312:79147, May 8 2010, 16:36:46)
> [GCC 4.4.4] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import zookeeper
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> ImportError: /usr/local/lib/python3.1/dist-packages/zookeeper.so: undefined
> symbol: PyString_AsString
> are there any plan to support Python3.X?
> I also tried to write a 3.1 ctypes wrapper but the C API seems in fact to be
> written in C++, so python ctypes cannot be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
