Deephaven Python Ticking Package
The pydeephaven-ticking package enables access to ticking Deephaven data from Python. It extends
the functionality of the pydeephaven package to add the ability to subscribe to tables and receive
change notifications containing added, removed, and modified data. It uses Cython to create a thin
wrapper around Deephaven's C++ library.
Prerequisites
Before installing this library, you will need to install the Deephaven Core C++ library and the
pydeephaven python package. All three packages (Deephaven Core C++, pydeephaven,
and pydeephaven-ticking) are present in the Deephaven Core GitHub repository. We assume you
have checked out this repository at the location specified by ${DHROOT}.
The Deephaven C++ client (and ticking Python client) are tested regularly on Ubuntu 22.04 x86_64. Additionally, successful tests have been run on RHEL 8 and Fedora 38 (both on x86_64).
To build on Windows, please see the file cpp-client/README-windows.md in this repository.
Installation
pydeephaven-ticking can be installed with pip or by building from source.
pip
A Linux operating system on x86_64 architecture is required to install via pip.
It's recommended to install this way in a Python virtual environment (venv).
pip install pydeephaven-ticking
Build from source
If building from source, pydeephaven-ticking also requires a working installation of the C++
client. All four packages (Deephaven Core, pydeephaven, pydeephaven-ticking, and the Deephaven
C++ client) are present in the deephaven-core
repository. It is assumed that you have the repository checked out at the location specified by
${DHROOT}.
Install the C++ client
First, install the Deephaven C++ client. Follow the instructions in $DHROOT/cpp-client/README.md.
Note the restrictions on supported platforms mentioned there. The instructions will ask you to
select a location for the installation of the C++ client library and its dependencies.
According to the C++ build instructions,
the location is specified in the ${DHCPP} environment variable.
Install pydeephaven
To install pydeephaven, follow the instructions in ${DHROOT}/py/client/README.md.
These instructions will require you to create a Python venv. After installing that package, you will continue to use that venv here.
Build the ticking Python client
Install Cython in the venv
If you've exited your venv, re-activate it.
# This assumes your venv is in $HOME/py/cython
source ~/py/cython/bin/activate
Then run
pip3 install cython
Build the shared library (Linux version)
cd ${DHROOT}/py/client-ticking
# Ensure the DHCPP environment variable is set per the instructions above
rm -rf build dist src/pydeephaven_ticking/_core.cpp # Ensure we clean the remnants of any pre-existing build.
DEEPHAVEN_VERSION=$(../../gradlew :printVersion -q) CPPFLAGS="-I${DHCPP}/include" LDFLAGS="-L${DHCPP}/lib" python3 setup.py build_ext -i
Install pydeephaven-ticking
Build the wheel with
DEEPHAVEN_VERSION=$(../../gradlew :printVersion -q) python3 setup.py bdist_wheel
Then install the package.
Note: the actual name of the .whl file may be different depending on system details.
pip3 install --force --no-deps dist/pydeephaven_ticking-<x.y>-cp310-cp310-linux_x86_64.whl
The --force flag is required to overwrite any previously-built version of the package that might
already be there. The --no-deps flag ensures that we are sure to refer to the pydeephaven
package just built from the above steps, rather than one from PyPi.
Testing the library
Run tests
$ python3 -m unittest discover tests
Sample Python program
Run python from the venv while in this directory, and try this sample Python program:
import pydeephaven as dh
import time
session = dh.Session() # assuming Deephaven Community Core is running locally with the default configuration
table = session.time_table(period=1000000000).update(formulas=["Col1 = i"])
listener_handle = dh.listen(table, lambda update : print(update.added()))
listener_handle.start()
# data starts printing asynchronously here
time.sleep(10)
listener_handle.stop()
session.close()
2 maintainers
Metadata
2 maintainers
Release files for pydeephaven-ticking 41.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| pydeephaven_ticking-41.11-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.17+ x86-64 | Details |
| pydeephaven_ticking-41.11-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.17+ x86-64 | Details |
| pydeephaven_ticking-41.11-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details |
| pydeephaven_ticking-41.11-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.17+ x86-64 | Details |
| pydeephaven_ticking-41.11-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.9 | CPython 3.9 | Linux glibc 2.17+ x86-64 | Details |
Total release size: 68.9 MB
Release files / pydeephaven_ticking-41.11-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pydeephaven_ticking-41.11-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 13.8 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
22e14155227a731c9e802307d33bb776092b83755b49e524a6da00740b93455d
|
|
BLAKE2b-256 checksum How to use checksums |
01524e2b10b803a776a8645f76ed123040237c29766337fe9f6a8f3e1a9b3265
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / pydeephaven_ticking-41.11-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pydeephaven_ticking-41.11-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 13.8 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
7043d9f128a22306fb5459031bfd38b3a0f1c1d46c43060d6507ddb2d706ab26
|
|
BLAKE2b-256 checksum How to use checksums |
d8c0e2646bcb697c22ac686fb7c7cea9a8d92de6a5264c5be779eb48dd63e99e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / pydeephaven_ticking-41.11-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pydeephaven_ticking-41.11-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 13.8 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
499dec0c8427d799c429db5354ffc5c73473a2f97c09a355ca2c93ff103a3eb6
|
|
BLAKE2b-256 checksum How to use checksums |
0d13089b63f8155317a8b2233aa14065ecaa27590ee008387c0ebdcce71df3e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / pydeephaven_ticking-41.11-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pydeephaven_ticking-41.11-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 13.8 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
aa93f4b70b70c0f1d2a24beea967c8312b1e32a1b453521ddced0db263c2990b
|
|
BLAKE2b-256 checksum How to use checksums |
8ed100c05bdb69988b0253667489576c2f358f87e54425f8044f443ba31e0f9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / pydeephaven_ticking-41.11-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | pydeephaven_ticking-41.11-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 13.8 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
3b9ec61e407842901195a533b575487a7722de08b45e483e270a87e8d3dcc501
|
|
BLAKE2b-256 checksum How to use checksums |
48711a9cf34a6640ce4d0c2d5a67f148c3944a8a1b312fa8934de33318f6d845
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency log
