semvec/pypi-packages huggingface dataset:
project-mjolnir 2.0.0
Modular D&D 3.5e Parser and Database Builder
License: MIT
Requires Python: >=3.10

# Project Mjölnir

Project Mjölnir is a modular, cross-platform parser and database builder for D&D 3.5e sourcebooks and indexes.

It automatically ingests `.docx` indexes for:
- Deities
- Feats
- Spells
- Mundane Items
- Magic Items
- Races
- Classes (Base + Prestige)
- Monsters (NPCs included)
- Templates

Parsed data is inserted into a clean SQLite database according to a relational schema.

Mjolnir includes:
- Modular parser system (one parser per entity type)
- Smart file type detection
- Text cleaning utilities
- Full logging and troubleshooting output
- Open structure for future VTT support and PC/NPC generators

**Mjolnir is designed to forge your D&D 3.5 source material into true power.**

## Usage

```bash
python mjolnir.py path_to_folder_or_file
```

Files are detected, parsed, and loaded into the database automatically.

.docx format required.
fancifypy 0.1.0
Code formatter to get less boring Python files
License: MIT
Requires Python: >=3.10

# Fancifypy

Are you tired of boring Python code?
Or do you want to make a real impression with your next PR?
Look no further!
Fancifypy will transform any plain and boring Python code into a feast for the eyes.

```python
pipx run fancifypy code "print(range(5))" --seed 42
```

```raw
ｐᵣⁱⁿｔ ( ᵣ𝙖𝕟ᵍ𝐞 ( 5 ) )
```

Alternatively, you can fancify files directly

```python
pipx run fancifypy path script.py
```

and defancified files (if you for some reason want boring files again)

```python
pipx run fancifypy boring script.py
```

Note that fancifypy leaves somewhat odd whitespaces, so we reccommend using [Ruff](https://docs.astral.sh/ruff/) or [Black](https://github.com/psf/black) afterwards to format the code.

## Is this safe?

Fancifypy checks that the abstract syntax tree doesn't change after fancifying, so this is 100% safe (for CPython).
This means that any code that imported your code before fancifying will also work with it after fancifying with no modifications.

## How does this work?

When CPython looks up identifiers, it first [normalizes the code using "NFKC" normalization](https://docs.python.org/3.6/reference/lexical_analysis.html#identifiers).
This program detects identifiers in a Python file and replaces all character with a different character that normalizes to it.
So for Python, there is no change in the files.