[Neo] Roadmap for the Python integration

Tobias Ivarsson tobias.ivarsson at neotechnology.com
Thu Mar 12 00:14:19 CET 2009


I have just committed an update to the Python bindings for Neo4j.

This update is a simplification over previous versions. Less code - better
maintainability.
* The API has been simplified to not have multiple ways of doing the same
thing. Previous versions supported most of the same methods as the Java API,
these have been removed in favor of a purely pythonic API.
* Support for Indexes has been added.
* As before the bindings work with both Jython and CPython. The code has
been refactored to better support having multiple backends. CPython is still
supported through JPype, but work on using JCC for the CPython backend has
been started.

The next steps that are planned from here are:
* Build a modelling system for defining domain models. This is in the works.
It's inspired by the Django model system and will also be able to integrate
with Django allowing Neo4j to be used for persistence for a Django website.
I demoed the first prototype of this at Devoxx last year.
* Refactor to support older and newer versions of the Python programming
language. The goal is to be able to use these bindings with Python 2.2 and
later versions (including 3.x). At this point it works with 2.5 and 2.6.
* Add support for more extension services. Ideally extension services should
be picked up and be useable automatically. At this point indexes is the only
supported extension service, and the support is hand coded.

At this point I would be happy if you could check it out, play with it and
submit bug reports.
The code is available at https://svn.neo4j.org/components/neo4j.py/trunk

-- 
Tobias Ivarsson <tobias.ivarsson at neotechnology.com>
Hacker, Neo Technology
www.neotechnology.com
Cellphone: +46 706 534857


More information about the User mailing list