Py2neo is a client library and comprehensive toolkit for working with Neo4j from within Python applications and from the command line. The core library has no external dependencies and has been carefully designed to be easy and intuitive to use.
1 maintainer
Metadata
1 maintainer
Release files for py2neo-history 3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| py2neo-history-3.tar.gz | 93.0 kB | Without provenance | Details |
Release files / py2neo-history-3.tar.gz
| Download URL | py2neo-history-3.tar.gz |
|---|---|
| Size | 93.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a2a6a706e997b491a29519aa50927531afa1528a9c55863065ae7c9ae07c9e4
|
|
BLAKE2b-256 checksum How to use checksums |
a03b25939949b4e0c3ed8e6b9531b54b212740b0b6a43385aea47e98a1acec4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0
|
Security for py2neo-history 3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
