nl_processing

Dutch language processing toolkit organized as a multi-package Python repository.

Install

pip install nl_processing

The published nl_processing package is the aggregate build from the repo root. Day-to-day development happens inside the package folders under packages/.

Repository Layout

packages/
  core/
  extract_text_from_image/
  extract_words_from_text/
  translate_text/
  translate_word/
  database/
  database_cache/
  sampling/
docs/
pyproject.toml        # aggregate build for the published nl_processing package
Makefile              # repo-wide lint/test entrypoint

Each package has its own:

• pyproject.toml
• ruff.toml
• pytest.ini
• tests/
• docs/

Modules

Development

Work inside one package when you only touch one module:

cd packages/translate_word
uv sync --all-groups
uv run pytest tests/unit

Run the repo-wide quality gate from the root:

make check

Useful package-local examples:

cd packages/core
uv run pytest tests/unit/core

cd packages/database
doppler run -- uv run pytest tests/integration/database

Dependency Rule

Modules are independent packages. Cross-module dependencies must be explicit in the consuming package's pyproject.toml.

Shared cross-module storage contracts live in nl_processing.core.ports. database and database_cache are concrete implementations and adapters, not the owners of those shared interfaces.

One intentional design change in this layout: database no longer imports translate_word directly. If you want automatic translation on add_words(), compose it explicitly:

from nl_processing.core.models import Language
from nl_processing.database.service import DatabaseService
from nl_processing.translate_word.service import WordTranslator

db = DatabaseService(
    user_id="alex",
    translator=WordTranslator(
        source_language=Language.NL,
        target_language=Language.RU,
    ),
)

Docs

• Repository module spec: docs/module-spec.md
• Environment variables: docs/ENV_VARS.md
• Release workflow: docs/REALEASE_WORKFLOW.md