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-history ~= 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.
.. image:: https://img.shields.io/pypi/v/py2neo.svg :target: https://pypi.python.org/pypi/py2neo :alt: PyPI version
.. image:: https://img.shields.io/pypi/dm/py2neo :target: https://pypi.python.org/pypi/py2neo :alt: PyPI Downloads
.. image:: https://img.shields.io/github/license/technige/py2neo.svg :target: https://www.apache.org/licenses/LICENSE-2.0 :alt: License
.. image:: https://coveralls.io/repos/github/technige/py2neo/badge.svg?branch=master :target: https://coveralls.io/github/technige/py2neo?branch=master :alt: Coverage Status
Py2neo is a client library and toolkit for working with Neo4j <https://neo4j.com/>_ from within Python <https://www.python.org/>_ applications.
The library supports both Bolt and HTTP and provides a high level API, an OGM, admin tools, a Cypher lexer for Pygments, and many other bells and whistles.
Command line tooling has been removed from the library in py2neo 2021.2. This functionality now exists in the separate ipy2neo project.
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.
To install the latest release of py2neo, simply use:
.. code-block:: bash
$ pip install py2neo
The following versions of Python and Neo4j (all editions) are supported:
.. list-table:: :header-rows: 1
* - Neo4j
- Python 3.5+
- Python 2.7
* - 4.3
- |test-neo43-py35+|
- |test-neo43-py27|
* - 4.2
- |test-neo42-py35+|
- |test-neo42-py27|
* - 4.1
- |test-neo41-py35+|
- |test-neo41-py27|
* - 4.0
- |test-neo40-py35+|
- |test-neo40-py27|
* - 3.5
- |test-neo35-py35+|
- |test-neo35-py27|
* - 3.4
- |test-neo34-py35+|
- |test-neo34-py27|
Note 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.
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
As of 2020, py2neo has switched to Calendar Versioning <https://calver.org/>_, 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.
For more information, read the handbook <http://py2neo.org/>_.
.. |test-neo43-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo43-py27 :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo43-py27" :alt: GitHub workflow status for tests against Neo4j 4.3 using py27
.. |test-neo43-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo43-py35+ :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo43-py35+" :alt: GitHub workflow status for tests against Neo4j 4.3 using py35+
.. |test-neo42-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo42-py27 :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo42-py27" :alt: GitHub workflow status for tests against Neo4j 4.2 using py27
.. |test-neo42-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo42-py35+ :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo42-py35+" :alt: GitHub workflow status for tests against Neo4j 4.2 using py35+
.. |test-neo41-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo41-py27 :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo41-py27" :alt: GitHub workflow status for tests against Neo4j 4.1 using py27
.. |test-neo41-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo41-py35+ :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo41-py35+" :alt: GitHub workflow status for tests against Neo4j 4.1 using py35+
.. |test-neo40-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo40-py27 :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo40-py27" :alt: GitHub workflow status for tests against Neo4j 4.0 using py27
.. |test-neo40-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo40-py35+ :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo40-py35+" :alt: GitHub workflow status for tests against Neo4j 4.0 using py35+
.. |test-neo35-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo35-py27 :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo35-py27" :alt: GitHub workflow status for tests against Neo4j 3.5 using py27
.. |test-neo35-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo35-py35+ :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo35-py35+" :alt: GitHub workflow status for tests against Neo4j 3.5 using py35+
.. |test-neo34-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo34-py27 :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo34-py27" :alt: GitHub workflow status for tests against Neo4j 3.4 using py27
.. |test-neo34-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo34-py35+ :target: https://github.com/technige/py2neo/actions?query=workflow%3A"test-neo34-py35+" :alt: GitHub workflow status for tests against Neo4j 3.4 using py35+
FAQs
Python client library and toolkit for Neo4j
We found that py2neo-history demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.