Skip to main content

EVEShip.fit's Dogma Engine for Python

PyPI Discord

This library calculates accurately statistics of an EVE Online ship fit.

The input are several data-files provided by EVE Online, together with a ship fit. The output are all the Dogma attributes of the ship, its items and the character.

The engine is written in Rust; this package wraps it, so every lookup happens inside Rust.

Install

The sde extra brings in eveshipfit-sde, which ships sde.dat.

pip install eveshipfit-dogma-engine[sde]

Usage

import esf_dogma_engine as dogma
from eveshipfit_sde import sde_path

build_number = dogma.load_sde_from_file(sde_path())

fit = {
    "ship": {"type_id": 587},
    "items": [
        {
            "type_id": 2873,
            "slot": {"type": "high", "index": 0},
            "state": "active",
            "charge": {"type_id": 185},
        }
    ],
    "character": {"skills": {3300: 5}},
}

calculation = dogma.calculate(fit)
# Or if you want to know the source of the effects:
with_sources = dogma.calculate(fit, {"sources": True})
# Or if you have a beacon in space (like wormhole effects):
with_beacon = dogma.calculate({**fit, "incoming": dogma.beacon(beacon_type_id)})
# Or if you have an EFT, the text format EVE copies a fit to the clipboard in:
imported = dogma.calculate(dogma.load_eft("[Rifter, My Rifter]\n200mm AutoCannon I"))
# And to write a fit back out as EFT:
eft = dogma.save_eft(fit)
# Or if you have a fitting a character saved in game, as ESI returns it (and the other way around):
from_esi = dogma.load_esi_fitting(fitting)
to_esi = dogma.save_esi_fitting(fit)
# Neither EFT nor ESI has states; with the skills set, this sets the ones EVE gives an imported fit:
settled = dogma.post_load({**from_esi, "character": {"skills": skills}})
# Or if you have a killmail, as ESI returns it, for the fit of the ship that died:
from_killmail = dogma.load_killmail(killmail)
# Or if you have an EVEShip.fit link, `<version>:<payload>`, with the payload gunzipped and unbase64'd:
from_link = dogma.load_link(version, payload)
# Or if you have an esf/1 document, as text or as a link (and the other way around):
from_esf = dogma.load_esf("%esf/1\nRifter\n200mm AutoCannon I\n")
from_esf_link = dogma.load_esf_link(link)
esf = dogma.save_esf(fit)
link = dogma.save_esf_link(fit)

# What EVE would not let you fly, in `violations` of the calculation:
validated = dogma.calculate(fit, {"validate": True})

load_sde_from_file may only be called once per process.

An EFT import matches the English names in sde.dat. To also match the other languages EVE supports, load names.dat as well:

from eveshipfit_sde import names_path

dogma.load_names_from_file(names_path())

Fits and calculations are plain dicts, typed with TypedDict in esf_dogma_engine.types. What every field means is explained under Input and output.

Every function but load_sde and load_names releases the GIL while it works, so a thread pool calculates fits in parallel.

More

How the engine works, the attributes EVEShip.fit adds and the fitting rules it validates are all in the main repository.

Metadata

Release files for eveshipfit-dogma-engine 13.3.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 eveshipfit-dogma-engine 13.3.0
File Size Uploaded Provenance Actions
eveshipfit_dogma_engine-13.3.0.tar.gz 129.1 kB With provenance Details for eveshipfit_dogma_engine-13.3.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for eveshipfit-dogma-engine 13.3.0
File Actions
eveshipfit_dogma_engine-13.3.0-cp310-abi3-win_amd64.whl CPython 3.10 abi3 Windows x86-64 Details for eveshipfit_dogma_engine-13.3.0-cp310-abi3-win_amd64.whl
eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.10 abi3 Linux glibc 2.17+ x86-64 Details for eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl CPython 3.10 abi3 Linux glibc 2.17+ ARM64 Details for eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
eveshipfit_dogma_engine-13.3.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl CPython 3.10 abi3 macOS 11.0+ ARM64, macOS 10.12+ universal2 (ARM64, x86-64), macOS 10.12+ x86-64 Details for eveshipfit_dogma_engine-13.3.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl

Total release size: 3.5 MB

Release files / eveshipfit_dogma_engine-13.3.0.tar.gz

Download URL eveshipfit_dogma_engine-13.3.0.tar.gz
Size 129.1 kB
Tags Source
SHA-256 checksum
How to use checksums
0dc36e0e1401413b7afeb70ae2d8ce86a80df90efe8e7ecfb82a8675472b4188
BLAKE2b-256 checksum
How to use checksums
2adc9c609bc9aa511aa95acc40f16ab37bcebad929c4c1927b71bfe0d8b66a46
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 4, 2026.

Transparency log

Release files / eveshipfit_dogma_engine-13.3.0-cp310-abi3-win_amd64.whl

Download URL eveshipfit_dogma_engine-13.3.0-cp310-abi3-win_amd64.whl
Size 567.0 kB
Tags CPython 3.10 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
c8e980ca93c771e9f1114b1c086234a7e41a6c9950ef3c287eb96f9e15cfb097
BLAKE2b-256 checksum
How to use checksums
8ce54107e2761e8199b9cd11ef68d4cea5f5bcc3505af3246367f0cac92a5edd
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 4, 2026.

Transparency log

Release files / eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 744.0 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
1894acdf3c3b7c280118b4b69a792507a9f7bbdaa7f96ce15558b8445508f9e3
BLAKE2b-256 checksum
How to use checksums
9ce2048c3825bf0f3595f6f4165c5384b87e2b9443cfe3f19961550485c4eb3e
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 4, 2026.

Transparency log

Release files / eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

Download URL eveshipfit_dogma_engine-13.3.0-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
Size 717.8 kB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 abi3
SHA-256 checksum
How to use checksums
68fd24947e27ce4ef5631d9b5262a953778a0f98e9f7c22862947cf7dfcfbcb2
BLAKE2b-256 checksum
How to use checksums
89cd8ce05e6aaf243299aeb24959b6cc757339f453d8f1d9a078e2d5dd64f40b
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 4, 2026.

Transparency log

Release files / eveshipfit_dogma_engine-13.3.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl

Download URL eveshipfit_dogma_engine-13.3.0-cp310-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl
Size 1.3 MB
Tags CPython 3.10 abi3 macOS 10.12+ universal2 (ARM64, x86-64) macOS 10.12+ x86-64 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
eab779049516420132dc8a5d2ea0a2cce1d03c2ee2d7631fc7112c62eae53613
BLAKE2b-256 checksum
How to use checksums
1dbf95fc49785ffcb49649f468bcb03ebc9d764b481fc05191bb12672ba51d97
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 4, 2026.

Transparency log

Security for eveshipfit-dogma-engine 13.3.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.

Full provenance

All 5 files in this release have been uploaded with provenance metadata.

Select from 5 files

Attestation for eveshipfit_dogma_engine-13.3.0.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 4, 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