Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

ISEKAI

ISEKAI is a general-purpose ETL framework for Django. It helps you migrate any data (including files) from any source into your Django models using a clear, pluggable pipeline. ISEKAI makes it simple to bring data from anywhere into Django models.

Why ISEKAI?

Django projects often need to bring data from a wide variety of sources into structured models, but writing ad-hoc scripts for this quickly becomes messy and repetitive. ISEKAI offers a clear, reusable framework for defining ETL pipelines so your migrations stay predictable, testable, and easy to maintain.

Concepts

At the core of ISEKAI is the Resource model. A Resource represents a single distinct piece of data you want to migrate. As it moves through the pipeline, the Resource accumulates data and undergoes transformations, and by the final stage it resolves to a single Django model instance. In other words, every Resource eventually becomes one record in your database, and the pipeline describes how it gets there.

The pipeline has five stages:

  1. Seed - Create the initial set of Resources, often by reading from a sitemap, CSV file, database table, or another source through custom seeders.
  2. Extract - Using those keys, fetch the raw bytes from the source, whether that's through the web with the HTTPExtractor or any other system via a custom extractor.
  3. Mine - Inspect extracted data to discover or 'mine" related Resources. For example, the HTMLImageMiner will create new Resources for each image it finds linked in an HTML page.
  4. Transform - Using the data on the Resource, produce a target Spec (your project's model-shaped representation) that the Load stage will create in Django.
  5. Load - Create the Django models from the Resource's Spec. This stage calculates the optimal build order for the objects, and can reconcile circular dependencies through a two-phase create mechanism.

Each stage is handled by processors. ISEKAI includes built-in processors for common use cases, but you can also write your own. This means you can extract resources from any source, apply custom transformations, and load into any Django model structure.

License

MIT

Metadata

Release files for isekai-django 0.1.0a7

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

Source distribution (sdist)

Source distribution for isekai-django 0.1.0a7
File Size Uploaded
isekai_django-0.1.0a7.tar.gz 449.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for isekai-django 0.1.0a7
File Interpreter ABI Platform
isekai_django-0.1.0a7-py3-none-any.whl Python 3 none any Details

Total release size: 486.3 kB

Release files / isekai_django-0.1.0a7.tar.gz

Download URL isekai_django-0.1.0a7.tar.gz
Size 449.5 kB
Tags Source
SHA-256 checksum
How to use checksums
0e53fd275ccb9ee756ee4f9d23212456c906412b705515a3f4f0a57c14a4065a
BLAKE2b-256 checksum
How to use checksums
ca2b1d76c20e922d27bbeaf9c936e5ed066e498d07fde5c351958013fed6760b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 20, 2025.

Transparency log

Release files / isekai_django-0.1.0a7-py3-none-any.whl

Download URL isekai_django-0.1.0a7-py3-none-any.whl
Size 36.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f708a717c3b70526b0588fc8bb08589f42d2966838c744f5616642b476cbd7b1
BLAKE2b-256 checksum
How to use checksums
5af97d716395a12c5ada46a5af3bb84f873c76eb625fb186947144d10e321778
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 20, 2025.

Transparency log
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