Skip to main content

Python client library and toolkit for Neo4j

Reason this release was yanked:

Broken dependency vendoring

Project description

This is a copy of the py2neo package to restore the version history that got deleted. It’s not possible to re-upload a deleted version of a package to PyPI. So if you rely on, for example, py2neo ~= 4.1.0 in your project, you can simply switch to py2neo-archive ~= 4.1.0. If your project works with py2neo 2021.2.3 or above, you can keep using py2neo as usual.

Note that this project will not get any updates past version 2021.2.3.

Py2neo

GitHub release License GitHub Workflow Status Coverage Status

Py2neo is a client library and toolkit for working with Neo4j from within Python applications and from the command line. The library supports both Bolt and HTTP and provides a high level API, an OGM, admin tools, an interactive console, a Cypher lexer for Pygments, and many other bells and whistles.

As of version 2021.1, Py2neo contains full support for routing, as exposed by a Neo4j cluster. This can be enabled using a neo4j://... URI or by passing routing=True to a Graph constructor.

Quick Example

To run a query against a local database is straightforward:

>>> from py2neo import Graph
>>> graph = Graph("bolt://localhost:7687", auth=("neo4j", "password"))
>>> graph.run("UNWIND range(1, 3) AS n RETURN n, n * n as n_sq")
   n | n_sq
-----|------
   1 |    1
   2 |    4
   3 |    9

Releases & Versioning

As of 2020, py2neo has switched to Calendar Versioning, using a scheme of YYYY.N.M. Here, N is an incrementing zero-based number for each year, and M is a revision within that version (also zero-based).

No compatibility guarantees are given between versions, but as a general rule, a change in M should require little-to-no work within client applications, whereas a change in N may require some work. A change to the year is likely to require a more significant amount of work to upgrade.

Note that py2neo is developed on a rolling basis, so patches are not made to old versions. Users will instead need to install the latest release to adopt bug fixes.

Installation

PyPI version PyPI Downloads

To install the latest release of py2neo, simply use:

$ pip install --upgrade py2neo

To install the latest stable code from the GitHub master branch, use:

$ pip install git+https://github.com/technige/py2neo.git@master#egg=py2neo

Requirements

Python versions Neo4j versions

The following versions of Python and Neo4j (all editions) are supported:

  • Python 2.7 / 3.4 / 3.5 / 3.6 / 3.7 / 3.8 / 3.9

  • Neo4j 3.4 / 3.5 / 4.0 / 4.1 / 4.2 / 4.3 (the latest point release of each version is recommended)

Py2neo provides support for the multi-database functionality added in Neo4j 4.0. More about this can be found in the documentation for the Graph class.

Note also that Py2neo is developed and tested under Linux using standard CPython distributions. While other operating systems and Python distributions may work, support for these is not available.

More

For more information, read the handbook.

Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

py2neo-archive-2021.1.3.tar.gz (182.7 kB view details)

Uploaded Source

File details

Details for the file py2neo-archive-2021.1.3.tar.gz.

File metadata

  • Download URL: py2neo-archive-2021.1.3.tar.gz
  • Upload date:
  • Size: 182.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/4.0.2 CPython/3.12.0

File hashes

Hashes for py2neo-archive-2021.1.3.tar.gz
Algorithm Hash digest
SHA256 4f3bcbdc9f05dc53e16e9c3b060092acdaa70bb8063bb211d98a4f8b2eb73621
MD5 f844faffc78bfb1647be1c1f134894b9
BLAKE2b-256 dc0bd9883c9c01951ad6700bf167f344346f5282407def82e7352c33a745257e

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page