entangled_evolution
Examples and documentation are provided as Jupyter notebooks.
Quick start (recommended)
This project uses uv, a fast Python package manager and virtual environment tool. You need to install uv on your system first. When that's done:
git clone https://github.com/dirkbrockmann/entangled_evolution.git
cd entangled_evolution
make notebook
Using entangled_evolution n your own code
import entangled_evolution
Installation via pip
You can now install entangled_evolution directly from PyPI:
pip install entangled_evolution
To install the latest development version from source:
pip install git+https://github.com/dirkbrockmann/entangled_evolution.git
Or clone and work with the code locally:
git clone https://github.com/dirkbrockmann/entangled_evolution.git
cd entangled_evolution
pip install -e .
Running the examples
To run the Jupyter notebook examples, install entangled_evolution with the extra dependencies:
pip install "entangled_evolution[examples]"
This will install all required packages for the example notebooks.
Running the benchmarks
To run the Jupyter notebook examples, install entangled_evolution with the extra dependencies:
pip install "entangled_evolution[bench]"
This will install all required packages for the example notebooks.
License
MIT
Metadata
Release files for entangled_evolution 0.2.0
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 | Actions |
|---|---|---|---|---|
| entangled_evolution-0.2.0.tar.gz | 12.1 kB | Without provenance | Details for entangled_evolution-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| entangled_evolution-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for entangled_evolution-0.2.0-py3-none-any.whl |
Total release size: 26.9 kB
Release files / entangled_evolution-0.2.0.tar.gz
| Download URL | entangled_evolution-0.2.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3d3100c0cfbee7c7745b806744a079609756661556e5f5385e203ac22e58ddb
|
|
BLAKE2b-256 checksum How to use checksums |
a01b6a8ed94d87d9f17db288cf100c8ea68cbb127861ef217ba2495e7e27e6fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / entangled_evolution-0.2.0-py3-none-any.whl
| Download URL | entangled_evolution-0.2.0-py3-none-any.whl |
|---|---|
| Size | 14.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4ca82475f9955b06c3789d9082999070e9ab42f00691c0b5b455510c2a82c45c
|
|
BLAKE2b-256 checksum How to use checksums |
2dc476ce67de0fc7f56b6215a1a3b931b97c8f316676c1c1e0b52bc273c2b231
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for entangled_evolution 0.2.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.