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.
Py2neo
======
.. 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.
Installation & Compatibility
----------------------------
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.
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 <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.
More
----
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+
Raw data
{
"_id": null,
"home_page": "https://py2neo.org/",
"name": "py2neo-history",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "",
"author": "Nigel Small",
"author_email": "technige@py2neo.org",
"download_url": "https://files.pythonhosted.org/packages/d1/63/b44482982412236656e8e4f78028b7ffcfea13997a3466e8d10001672bec/py2neo-history-2021.2.3.tar.gz",
"platform": null,
"description": "This is a copy of the py2neo package to restore the version history that got deleted.\nIt's not possible to re-upload a deleted version of a package to PyPI.\nSo if you rely on, for example, `py2neo ~= 4.1.0` in your project, you can simply switch to `py2neo-history ~= 4.1.0`.\nIf your project works with py2neo 2021.2.3 or above, you can keep using `py2neo` as usual.\n\nNote that this project will not get any updates past version 2021.2.3.\n\nPy2neo\n======\n.. image:: https://img.shields.io/pypi/v/py2neo.svg\n :target: https://pypi.python.org/pypi/py2neo\n :alt: PyPI version\n\n.. image:: https://img.shields.io/pypi/dm/py2neo\n :target: https://pypi.python.org/pypi/py2neo\n :alt: PyPI Downloads\n\n.. image:: https://img.shields.io/github/license/technige/py2neo.svg\n :target: https://www.apache.org/licenses/LICENSE-2.0\n :alt: License\n\n.. image:: https://coveralls.io/repos/github/technige/py2neo/badge.svg?branch=master\n :target: https://coveralls.io/github/technige/py2neo?branch=master\n :alt: Coverage Status\n\n\n**Py2neo** is a client library and toolkit for working with `Neo4j <https://neo4j.com/>`_ from within `Python <https://www.python.org/>`_ applications.\nThe 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.\n\nCommand line tooling has been removed from the library in py2neo 2021.2.\nThis functionality now exists in the separate **ipy2neo** project.\n\nAs of version 2021.1, py2neo contains full support for routing, as exposed by a Neo4j cluster.\nThis can be enabled using a ``neo4j://...`` URI or by passing ``routing=True`` to a ``Graph`` constructor.\n\n\nInstallation & Compatibility\n----------------------------\n\nTo install the latest release of py2neo, simply use:\n\n.. code-block:: bash\n\n $ pip install py2neo\n\nThe following versions of Python and Neo4j (all editions) are supported:\n\n.. list-table::\n :header-rows: 1\n\n * - Neo4j\n - Python 3.5+\n - Python 2.7\n * - 4.3\n - |test-neo43-py35+|\n - |test-neo43-py27|\n * - 4.2\n - |test-neo42-py35+|\n - |test-neo42-py27|\n * - 4.1\n - |test-neo41-py35+|\n - |test-neo41-py27|\n * - 4.0\n - |test-neo40-py35+|\n - |test-neo40-py27|\n * - 3.5\n - |test-neo35-py35+|\n - |test-neo35-py27|\n * - 3.4\n - |test-neo34-py35+|\n - |test-neo34-py27|\n\nNote that py2neo is developed and tested under **Linux** using standard CPython distributions.\nWhile other operating systems and Python distributions may work, support for these is not available.\n\n\nQuick Example\n-------------\n\nTo run a query against a local database is straightforward::\n\n >>> from py2neo import Graph\n >>> graph = Graph(\"bolt://localhost:7687\", auth=(\"neo4j\", \"password\"))\n >>> graph.run(\"UNWIND range(1, 3) AS n RETURN n, n * n as n_sq\")\n n | n_sq\n -----|------\n 1 | 1\n 2 | 4\n 3 | 9\n\n\nReleases & Versioning\n---------------------\n\nAs of 2020, py2neo has switched to `Calendar Versioning <https://calver.org/>`_, using a scheme of ``YYYY.N.M``.\nHere, ``N`` is an incrementing zero-based number for each year, and ``M`` is a revision within that version (also zero-based).\n\nNo compatibility guarantees are given between versions, but as a general rule, a change in ``M`` should require little-to-no work within client applications,\nwhereas 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.\n\nNote that py2neo is developed on a rolling basis, so patches are not made to old versions.\nUsers will instead need to install the latest release to adopt bug fixes.\n\n\nMore\n----\n\nFor more information, read the `handbook <http://py2neo.org/>`_.\n\n\n.. |test-neo43-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo43-py27\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo43-py27\"\n :alt: GitHub workflow status for tests against Neo4j 4.3 using py27\n\n.. |test-neo43-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo43-py35+\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo43-py35+\"\n :alt: GitHub workflow status for tests against Neo4j 4.3 using py35+\n\n.. |test-neo42-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo42-py27\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo42-py27\"\n :alt: GitHub workflow status for tests against Neo4j 4.2 using py27\n\n.. |test-neo42-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo42-py35+\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo42-py35+\"\n :alt: GitHub workflow status for tests against Neo4j 4.2 using py35+\n\n.. |test-neo41-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo41-py27\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo41-py27\"\n :alt: GitHub workflow status for tests against Neo4j 4.1 using py27\n\n.. |test-neo41-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo41-py35+\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo41-py35+\"\n :alt: GitHub workflow status for tests against Neo4j 4.1 using py35+\n\n.. |test-neo40-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo40-py27\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo40-py27\"\n :alt: GitHub workflow status for tests against Neo4j 4.0 using py27\n\n.. |test-neo40-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo40-py35+\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo40-py35+\"\n :alt: GitHub workflow status for tests against Neo4j 4.0 using py35+\n\n.. |test-neo35-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo35-py27\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo35-py27\"\n :alt: GitHub workflow status for tests against Neo4j 3.5 using py27\n\n.. |test-neo35-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo35-py35+\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo35-py35+\"\n :alt: GitHub workflow status for tests against Neo4j 3.5 using py35+\n\n.. |test-neo34-py27| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo34-py27\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo34-py27\"\n :alt: GitHub workflow status for tests against Neo4j 3.4 using py27\n\n.. |test-neo34-py35+| image:: https://img.shields.io/github/workflow/status/technige/py2neo/test-neo34-py35+\n :target: https://github.com/technige/py2neo/actions?query=workflow%3A\"test-neo34-py35+\"\n :alt: GitHub workflow status for tests against Neo4j 3.4 using py35+",
"bugtrack_url": null,
"license": "Apache License, Version 2.0",
"summary": "Python client library and toolkit for Neo4j",
"version": "2021.2.3",
"project_urls": {
"Bug Tracker": "https://github.com/technige/py2neo/issues",
"Documentation": "https://py2neo.org/2021.2/",
"Homepage": "https://py2neo.org/",
"Source Code": "https://github.com/technige/py2neo"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "d163b44482982412236656e8e4f78028b7ffcfea13997a3466e8d10001672bec",
"md5": "72e63478b5ec70f84f45d4bf69490edc",
"sha256": "21a294ee171450e97a240bf5e40a5a47fb345de9a65531543aae65e7ee903992"
},
"downloads": -1,
"filename": "py2neo-history-2021.2.3.tar.gz",
"has_sig": false,
"md5_digest": "72e63478b5ec70f84f45d4bf69490edc",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 162028,
"upload_time": "2023-10-20T15:18:04",
"upload_time_iso_8601": "2023-10-20T15:18:04.764315Z",
"url": "https://files.pythonhosted.org/packages/d1/63/b44482982412236656e8e4f78028b7ffcfea13997a3466e8d10001672bec/py2neo-history-2021.2.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-10-20 15:18:04",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "technige",
"github_project": "py2neo",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "py2neo-history"
}
JSON
