Skip to main content

spexial

scipy.special in JAX

PyPI version PyPI platforms Actions Status codecov Documentation

spexial provides special functions for JAX, following the scipy.special API. The implementations are written in terms of JAX primitives, so they compose with jit, grad and vmap, and run on CPU, GPU and TPU.

It exists to fill gaps in jax.scipy.special: zeta accepts negative integers where JAX returns nan, spence accepts complex arguments where JAX is real-only, and the modified Bessel K, Gegenbauer and polylogarithm functions have no JAX counterpart at any version. Where SciPy already covers a case, spexial matches it rather than claiming to exceed it.

Installation

pip install spexial

or

uv add spexial

Example

>>> import jax
>>> jax.config.update("jax_enable_x64", True)

>>> import jax.numpy as jnp
>>> import spexial as sp

>>> # Gegenbauer polynomial C_n^alpha(x), matching scipy.special.eval_gegenbauer
>>> sp.eval_gegenbauer(3, 0.5, 0.25)
Array(-0.3359375, dtype=float64, weak_type=True)

Everything is vectorisable and differentiable in the usual way:

>>> xs = jnp.linspace(-1.0, 1.0, 5)
>>> jax.vmap(lambda x: sp.eval_gegenbauer(3, 0.5, x))(xs)
Array([-1.    ,  0.4375, -0.    , -0.4375,  1.    ], dtype=float64)

What is here

Function scipy.special counterpart
comb comb (the exact=False variant)
gamma gamma — JAX's value, plus an analytic derivative
eval_gegenbauer eval_gegenbauer
eval_gegenbauers -- returns every order up to n
K0, K1, K2 k0, k1, kn
K0e, K1e, K2e k0e, k1e, kve — scaled by e^z, no upper limit
Li -- the polylogarithm
spence spence — complex too, which JAX rejects
zeta zeta — negative integers, which JAX gives as nan

Read Accuracy and domains before relying on any of these. It records, per function, the domain each is tested over and the tolerance it actually meets. Some are not machine-precision — the modified Bessel functions are accurate to about 1e-7, and zeta does not implement the critical strip.

Documentation

https://jaxtronomy.github.io/spexial

Development

We welcome contributions! See CONTRIBUTING.md.

uv sync --group dev
uv run nox -s all      # lint -> test -> docs

Citation

If you use spexial in work you publish, please cite it — see CITATION.cff. Several routines originate in the LINX code.

License

MIT. See LICENSE.

Metadata

Release files for spexial 0.1.1

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

Source distribution (sdist)

Source distribution for spexial 0.1.1
File Size Uploaded Provenance Actions
spexial-0.1.1.tar.gz 167.1 kB With provenance Details for spexial-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for spexial 0.1.1
File Interpreter ABI Platform Actions
spexial-0.1.1-py3-none-any.whl Python 3 none any Details for spexial-0.1.1-py3-none-any.whl

Total release size: 230.9 kB

Release files / spexial-0.1.1.tar.gz

Download URL spexial-0.1.1.tar.gz
Size 167.1 kB
Tags Source
SHA-256 checksum
How to use checksums
84caecbaa1b35e3aeac3ad3914704653e850448ade08190d3d7cdf10377c82d3
BLAKE2b-256 checksum
How to use checksums
d7052be3491efda7092f1694b7bce6b61073057dff55521e9f896418e1e782bd
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 19, 2026.

Transparency log

Release files / spexial-0.1.1-py3-none-any.whl

Download URL spexial-0.1.1-py3-none-any.whl
Size 63.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8deeb6475da2fbb44318d6904aa50edc02c274f2fcbcb78e56264f81c6ee88cc
BLAKE2b-256 checksum
How to use checksums
2f66c0be6fc8693741c69d1646f4ff92f1959f346454f1aa1fc2271cbb3e4d2f
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 19, 2026.

Transparency log

Security for spexial 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.

Select from 2 files

Attestation for spexial-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 Oct 19, 2026.

Transparency log

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