murex
What simulations of artists' media share. The murex is the sea snail Tyrian purple was made from; this is where oilpaint and fusain get their colour.
Pigmentandmurex.spectral: colours as pigments that mix like the real thing (blue and yellow give green, not grey), using spectral Kubelka-Munk theory over 24 bands.Bezier,CatmullRom,Polyline: stroke paths resampled by arc length, and values that vary along a stroke.murex.noise: textures (paper, weaves, wood grain).Reference: a reference image, asked for its colour, direction and detail at the scale of the tool in hand.write_pngandmurex.filters: output and small image filters.
from murex import Pigment, mix_colors
mix_colors(["#1b3fa0", "#f5d000"]) # a green
glaze = Pigment("#8e1b2c", opacity=0.3) # a transparent crimson
glaze.appearance(thickness=1.0, over="#f2c80f")
Development
uv sync --group dev --frozen # install the package and the development tools
uv run pytest # run the tests
make pre-push # what CI runs: tox, coverage, spelling
License
1 maintainer
Metadata
1 maintainer
Release files for murex 0.1.1
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 |
|---|---|---|---|---|
| murex-0.1.1.tar.gz | 90.6 kB | With provenance | Details for murex-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| murex-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for murex-0.1.1-py3-none-any.whl |
Total release size: 116.6 kB
Release files / murex-0.1.1.tar.gz
| Download URL | murex-0.1.1.tar.gz |
|---|---|
| Size | 90.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f5c080916209dd59b10b19fbc26adff04c449cfa0b8d79f00cf74cddd44bf9f
|
|
BLAKE2b-256 checksum How to use checksums |
c8d5be92a3f673115edfea5ccf0ec81b9f5ccf1be298f73d1a1a962b90110699
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logRelease files / murex-0.1.1-py3-none-any.whl
| Download URL | murex-0.1.1-py3-none-any.whl |
|---|---|
| Size | 26.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8001ed93d4bc64ac3ccca7d49b00357717cc485fe4bae1d6fc892989f3e864c3
|
|
BLAKE2b-256 checksum How to use checksums |
1c6d617c5c1bb8b23a99358c7e9fe87c0004472e252dd08d1e88c76cbb213345
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logSecurity for murex 0.1.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for murex-0.1.1.tar.gz
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 Nov 12, 2026.
Transparency logA 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.
