adiumentum 0.1.1

No project description provided

adiumentum

Running this project requires copier, git, uv, and flake. Install nix and install the others by running nix-shell -p uv python3 git. You can now copy the project and run the toy CLI provided out-of-the-box:

copier copy --trust \
    /home/isaac/repos/dev-envs/python-uv-nix /tmp/hello-world \
    --data-file /home/isaac/repos/dev-envs/python-uv-nix/example-data-uv.yml

nix run /tmp/hello-world

You can also enter a development environment with all dependencies installed:

nix develop

Once in this dev shell, you have a number of development utils you can try out (via just):

✔just
✔just format
✔just check
✔just fix
✔just typecheck
✔just lint
✔just deal
✔just vulture
✔just pydeps-full
✔just pydeps
✔just pydeps-simple
✔just view-deps
✔just snakefood
✔just deply
✔just bandit
✔just bandit-html
✔just bandit-view
✔just pyflame
✔just flamegraph
✔just perf-flamegraph
✔just check-structure
✔just check-imports
✔just smoke
✔just unit
✔just test
✔just test-cov
✔just docs
✔just scalene
✔just view-cov
✔just view-docs
✔just view-flamegraphs
✔just sbom

lefthook validate
lefthook run all

Roadmap

0. ✔ Sync package lists in uv.nix.jinja and README.md

1. ✔ Parametrize each package for copier and update copier.yml

2. ✔ Clean up copier.yml and example-data.yml

3. ✔ Get impure environment working -> draw from buildFHSUserEnv approach in consilium and other projects

4. ✔ Write working version of scripts and test them on datethyme

5. ✔ create reference project (revised from datethyme)

6. ✔ use copier to re-create it (make a datethyme answers file)

7. ✔ find good CLI tools for diffing an entire folder

8. ✔ iteratively modify template until copier perfectly re-creates the reference project

9. ✔ package mdformat with mdformat-mkdocs (via nix)

10. ✔ remove super-linter, but look over it and steal any good ideas

11. ✔ add commitizen and commitmsgfmt ✔

12. ✔ Modify nix to support any python version via nixpkgs-python and tox

13. ✔ Read through jinja2-ansible-filters

14. Go through https://www.youtube.com/results?search_query=nix+and+python and any relevant NixCon talks

15. ✔ restructure nix code

16. ✔ add poetry support (selectable via copier)

17. re-make datethyme package using template, iteratively polishing the template

18. add copier switch to include a CLI or not

Later

Note: first get working the way it is for datathyme.

0. conventional-changelog

1. Package all docs packages via nix, since they run independently of the other Python packages.

2. Do the same for testing dependencies, if possible.

3. Add different types of git hooks

• Client-Side Hooks

  • Pre-commit hooks run before a commit is created and are ideal for code quality checks. They're perfect for running linters, formatters, static analysis tools, or tests to catch issues before they enter the repository. If the hook exits with a non-zero status, the commit is aborted

  • Prepare-commit-msg hooks execute after the default commit message is created but before the editor opens. These work well for automatically adding ticket numbers, branch names, or standardized formatting to commit messages based on branch patterns or other context

  • Commit-msg hooks run after you've written your commit message and are excellent for enforcing commit message conventions. They can validate that messages follow specific formats, contain required information like issue references, or meet length requirements

  • Post-commit hooks trigger after a commit completes successfully. Since they can't affect the commit outcome, they're useful for notifications, triggering builds, updating external systems, or logging commit information

  • Pre-rebase hooks run before rebasing and help prevent rebasing published commits or branches that shouldn't be rebased. They're particularly valuable for protecting main branches or enforcing workflow policies

  • Post-checkout and post-merge hooks execute after checking out branches or completing merges. These are ideal for environment setup tasks like updating dependencies, clearing caches, generating files, or syncing external resources that depend on the current branch state

• Server-Side Hooks

  • Pre-receive hooks run before any references are updated when receiving a push. They're powerful for enforcing repository-wide policies like preventing force pushes to protected branches, validating that all commits meet standards, or checking permissions before allowing updates

  • Update hooks execute once per branch being updated and are perfect for branch-specific policies. They can enforce different rules for different branches, validate individual commits, or check that updates follow branching strategies

  • Post-receive hooks run after all references are successfully updated and are ideal for deployment triggers, sending notifications, updating issue trackers, or kicking off CI/CD pipelines. Since they run after the push succeeds, they're commonly used for automation that depends on the repository being in its new state

Dependency Classes

Dependency Classes

TODO: look at jj-fzf, lazyjj, gg-jj look at luxuries

• dependency resolution (should already be installed)

  • uv ✔

• miscellaneous (semver via Python)

  • semver ✔

• task running / hooks (installable via Python or Nix; Nix preferred)

  • just ✔
  • lefthook ✔

• interactive programming (installable via Python or Nix; Nix preferred)

  • ipython ✔

• static type checking (installable via Python or Nix; Nix preferred)

  • mypy ✔
  • ty ✔

• source code visualization (graphviz and pydeps via Nix, the rest via Python)

  • pydeps ✔
  • graphviz ✔
  • deply ✔
  • snakefood3 ✔
  • grimp ✔

• performance profiling (flamegraph and scalene via Nix, pyflame via Python)

  • pyflame ✔
  • scalene ✔
  • flamegraph-rs (cargo-flamegraph in nix) ✔

• software supply chain, security (installable via Python, but Nix preferred)

  • cyclonedx-python ✔
  • bandit ✔

• testing (installed via Python for now)

  • pytest ✔
  • pytest plugins: --> look at these
    • mock ✔
    • testmon ✔
    • cov ✔
    • loguru ✔
    • profiling video ✔
  • coverage ✔
  • hypothesis ✔
  • tox ✔

• docs (installed via Python for now)

  • mkdocs ✔
  • mkdocstrings ✔
  • mkdocstrings-python ✔
  • mkdocs-material ✔
  • pygments ✔

• formatters / linters

  • installable via Python or Nix:
    • ruff ✔
    • mdformat + mdformat-mkdocs TODO
    • yamlfmt OR yamllint ✔
    • pyprojectsort
    • toml-sort ✔
  • installable only via Nix or other package manager:
    • treefmt + treefmt-nix ✔
    • alejandra ✔
    • super-linter TODO
    • markdown-code-runner OR mdsf ✔
    • markdownlint-cli2 OR markdownlint-cli TODO
    • just-formatter ✔

To Look at for Later

• pystackflame