Skip to main content

Cymple - Cypher Modular Pythonic Language Extension

A productivity tool for creating Cypher queries in Python.

Documentation Status Python package

About the project

Cymple is a lightweight Python package for creating queries in Cypher, Neo4j's graph database query language. Give it a try, it's 'Cymple'!

Consider using Cymple if you want:

  • auto-completion for writing Cypher
  • to write compound Cypher queries without getting involved with strings
  • to write Cypher queries in a scalable and extensible manner
  • to be able to easily reuse Cypher queries across your code

image

Getting Started

Setup

pip install cymple

Examples

Simple Example

Let's take a look at the following snippet.

from cymple import QueryBuilder

qb = QueryBuilder()
query = qb.match().node(labels='Person', ref_name='p')
query = query.where('p.name', '=', '"Michelle"').return_literal('p')
print(query)

This snippet will output the following Cypher query:

MATCH (p: Person) WHERE p.name = "Michelle" RETURN p

See the samples directory for examples.

Cymple is intended for creating Cypher queries in Python, rather than executing queries on an actual DB.
For executing queries, see Neo4j's Bolt driver for Python. See also neo4j_e2e.py in the samples directory.

Autocompletion

Cymple is designed to provide autocompletion on IDEs that support autocompletion. This feature is context aware with respect to the current query being written.

gif1

Reusing Queries

Two queries can be combined to a create a new one.

qb = QueryBuilder()
query1 = qb.match().node(labels='Person', ref_name='p').with_('p')
query2 = qb.match().node(labels='Person', ref_name='q').related_to('friend_of').node(ref_name='p')
query = query1 + query2
print(query)

This snippet will output the following Cypher query:

MATCH (p: Person) WITH p MATCH (q: Person)-[: friend_of]->(p)

Prerequisites

  • Python 3.8+

Contributing

Intro

We encourage you to help us to improve this package! These instructions will give you a copy of the project up and running on your local machine for development and testing purposes.

Installing a Development Environment

# Set virtual environment.
python -m venv .venv
source .venv/bin/activate

# Upgrade pip

# Install development dependencies.
# Tools needed for deployment and packaging will be installed now.

pip install -r requirements-dev.txt

Development tools configurations

  • setuptools is configured in setup.cfg

  • pycodestyle is configured in setup.cfg

  • coverage.py is configured in pyproject.toml

Testing

pytest is used as a test runner.

pytest configurations reside in pyproject.toml

pytest fixtures are stored in tests/conftest.py file.

How-to run tests:

# Install test requirements.

pip install -r requirements-test.txt

# Run tests.
# All the tests under tests/ directory will be run.

pytest --cov=cymple

Adding a new Cypher clause

Adding a new Cypher clause to Cymple consists of few simple steps:

  1. Go to src/cymple/internal/declarations/. This directory contains all supported clause declarations.
  2. Add a json file describing the clause and the method(s) interfaces(s) of the new clause that you would like to add to the builder. If you do it for the first time, take a look at existing json files of currently supported Cypher clauses.
  3. Identify all the existing clauses that can precede your new clause, and add your new clause's name to the 'successors' list of those clauses' JSONs.
  4. Run python src/cymple/internal/internal_renderer.py. This script generates a new builder.py file with all clauses that were declared in src/cymple/internal/declarations/.
  5. By default, by adding a declaration json file, the internal_builder.py script takes the declared clause and generates a method that simply concatenates your new clause to the builder's current query. However, if you need anything more complex than that, you can write your own implementation by creating a new method with your clause's name at src/cymple/internal/overloads/. Don't forget to run python src/cymple/internal/internal_renderer.py again :)
  6. If you're satisfied with the new clause, add a unit test in test_clauses.py and make sure it generates the expected Cypher string.

Generating Documentation

Make sure you run:

pip install -r requirements-dev.txt

or

pip install sphinx

to proceed.

To generate a new HTML documentation, run:

cd docs
make clean html
make html

Versioning

Semantic Versioning is used for versioning.

For the versions available, see the tags on the repository.

Current version is stored in src/cymple/version.py.

Project structure

cymple/
├── docs/   # Project documentation
├── pyproject.toml  # Development and packaging tools configurations
├── README.md  # Project general information
├── requirements-dev.txt  # Development dependencies, such as packaging tools, etc.
├── requirements-test.txt  # Test dependencies
├── requirements.txt       # Pinned versions of all the end-user dependency tree
├── setup.cfg  # packaging tool configurations
├── setup.py   # Packaging script
├── src/  # All source code
│   └── cymple/  # Cymple source code
│       ├── internal/  # Cypher builder internal renderer
│       │   ├── declarations/        # clause declarations
│       │   ├── overloads/           # custom clause implementations
│       │   ├── finale.py            # A part of the rendered code that comes last
│       │   ├── internal_renderer.py # Internal renderer implementation for creating Cymple's user-facing code
│       │   └── preface.py           # A part of the rendered code that comes first
│       ├── __init__.py  # Package initialization
│       ├── __main__.py  # Main script when run as a command line tool
│       ├── builder.py   # Query Builder implementation
│       ├── typedefs.py  # Query Builder typedefs to be used in Cymple's API
│       └── version.py   # Package version
└── tests/  # Tests
    ├── conftest.py  # Fixtures
    ├── data/  # Tests data files, such as input/output files, mocks, etc.
    ├── e2e/   # End-to-End functional tests
    ├── integration  # Integration tests
    └── unit  # Unit tests
        ├── __init__.py
        └── test_real_use_cases.py  # Test project startup

Metadata

Release files for cymple 0.12.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cymple 0.12.0
File Size Uploaded Provenance Actions
cymple-0.12.0.tar.gz 14.7 kB Without provenance Details for cymple-0.12.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cymple 0.12.0
File Interpreter ABI Platform Actions
cymple-0.12.0-py2.py3-none-any.whl Python 3, Python 2 none any Details for cymple-0.12.0-py2.py3-none-any.whl

Total release size: 26.7 kB

Release files / cymple-0.12.0.tar.gz

Download URL cymple-0.12.0.tar.gz
Size 14.7 kB
Tags Source
SHA-256 checksum
How to use checksums
25fffe86e723b369f2fb15a00a4f1fdc3962f2bb43fbe7a51e622b676a8dcf3d
BLAKE2b-256 checksum
How to use checksums
03ec337f30befe8bffca9c82df7fa65e10f4ed93380e18d8b1d6910a7fbea930
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.7

Release files / cymple-0.12.0-py2.py3-none-any.whl

Download URL cymple-0.12.0-py2.py3-none-any.whl
Size 12.0 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
783b21242accd4db320623afad7acf366cf84129f15125c2f5112f231c17ba7a
BLAKE2b-256 checksum
How to use checksums
25106b255e08be93b41242048d6ce267ee10dc2db15a524e0cef7c8d8bbd9e20
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.7

Security for cymple 0.12.0

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page