Henry Robinson commented on ZOOKEEPER-395:
Yes, you'll need the Python development headers installed. For yum-based
systems these are packaged in python-devel. These are a dependency for building
the module, but not installing it. I'm not sure if adding ant rules to
automatically download the package is the right thing to do, as people often
like to manage those things themselves, and version matching will be complex. I
should at least add a warning to the readme.
I think that the module will build correctly against 2.3 (and I'll be really
interested to hear about your experiences when you get Python.h installed),
however it certainly won't build against anything earlier than that (as PyGIL*
were introduced in 2.3 which we need to get callbacks working). I don't use
many fancy features, so I hope to be safe. I've built it against 2.5.1 here,
and have a 2.6 system I can try. I expect 3.0 might have changed the API
though, so I doubt the module will work there.
> Python bindings
> Key: ZOOKEEPER-395
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-395
> Project: Zookeeper
> Issue Type: New Feature
> Affects Versions: 3.2.0
> Reporter: Henry Robinson
> Assignee: Henry Robinson
> Attachments: ZOOKEEPER-395.patch, ZOOKEEPER-395.patch
> ZooKeeper doesn't have Python bindings. Having them would be useful, and
> would complement the extant Perl bindings.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.