Recent commits to derivepassphrase.git (4fc0971da8df2739d5181e2b7ca247c30ae3f368)

Fix typos in the documentation

2026-08-09T17:18:56+02:00

</pre>

Update wishlist to post-v0.6.1

2026-07-06T21:29:46+02:00

</pre>

Release 0.6.1

2026-07-06T21:28:06+02:00

</pre>

Merge branch 'release-0.6.1-preparations'

2026-07-06T21:20:40+02:00

Prepare to release derivepassphrase v0.6.1

* release-0.6.1-preparations:
  Update wishlist
  Update the translation template, the German translation, and the message catalogs
  Add changelog entries for economic-test-suite, click-8.4.2-compatibility and openssh-bug3967-workaround
  Reformat everything with ruff
  Update wishlist
  Set the Python path correctly during pytest invocation
</pre>

Update wishlist

2026-07-06T20:19:03+02:00

Also reference the new entry in the changelog.
</pre>

Update the translation template, the German translation, and the message catalogs

2026-07-05T22:34:45+02:00

</pre>

Add changelog entries for economic-test-suite, click-8.4.2-compatibility and openssh-bug3967-workaround

2026-07-05T22:22:00+02:00

</pre>

Reformat everything with ruff

2026-07-05T21:47:45+02:00

Linting and type checking passes, so nothing to do there.
</pre>

Update wishlist

2026-07-05T21:46:51+02:00

</pre>

Set the Python path correctly during pytest invocation

2026-07-05T21:31:22+02:00

Some of our tests spawn subprocesses, and without this, the subprocesses
fail to import code from the `tests` hierarchy (e.g., `tests.data`.)

We have so far sidestepped this issue by requiring `$PYTHONPATH` to be
set accordingly, but it turns out that setting this in the pytest
settings works even more reliably.

In the long run, it might be smarter to use a similar source layout
in `tests` as we already do in `src`: a top-level
`test_derivepassphrase` package, and the `data`, `machinery` and other
tests modules/packages as submodules/subpackages of
`test_derivepassphrase`.
</pre>