Recent commits to derivepassphrase.git (d539649e3f89b92ff3123ebd8a2dddce40f24719)

Merge topic branch 'cleanup-lockfiles-in-test-harness' into master

2025-04-09T19:29:34+02:00

* cleanup-lockfiles-in-test-harness:
  Clean up configuration write lock files in the test suite
</pre>

Clean up configuration write lock files in the test suite

2025-04-09T19:27:50+02:00

When using a temporary, isolated `derivepassphrase` configuration
directory in the test suite, also clean up the matching configuration
write lock file, which is not located in the configuration directory.
</pre>

Merge topic branch 'selection-menu-to-stderr' into master

2025-04-09T19:24:00+02:00

* selection-menu-to-stderr:
  Emit selection menu to standard error
</pre>

Emit selection menu to standard error

2025-04-09T19:20:13+02:00

Consider the heading and the menu printed before a prompt as diagnostic
information, and output it to standard error.
</pre>

Merge topic branch 'abstract-cli-runner' into master

2025-04-09T19:17:57+02:00

* abstract-cli-runner:
  Wrap click.testing.CliRunner to directly return a ReadableResult
</pre>

Wrap click.testing.CliRunner to directly return a ReadableResult

2025-04-09T19:16:36+02:00

Instead of using `click.testing.CliRunner` directly and transforming the
result, wrap the runner in a new class that does the necessary
transformations on the result automatically.

This indirection of the CLI runner also allows the wrapper to cope with
(some) incompatible changes in `click` across versions, or even
eventually swap out the underlying implementation completely.

As a first incompatibility to bridge, `click` 8.2.0 (currently in beta)
merges many bad or incomplete fixes for long-standing issues, but with
no regard to backward compatibility.  Of particular relevance,
`click.testing.CliRunner` no longer accepts the `mix_stderr`
argument,[^1] and the meanings of the `output` and the `stdout`
attribute of `click.testing.Result` have changed.[^2]  These two
incompatibilities are handled by the wrapper.

  [^1]: This breaks practically every call to the runner: `mix_stderr`
  defaults to `True`, thus the default behavior is to mangle the output
  streams.  Why would you want that, in your testing machinery no less,
  where automatically mangling or discarding information behind the
  scenes is detrimental to debugging?!  As a consequence, `mix_stderr`
  *has* to be specified if you want output streams not to be mangled,
  and if you want them to be mangled, you *should* specify `mix_stderr`
  explicitly.  So basically, you always specify `mix_stderr`.  And thus
  removing the (definition of the) `mix_stderr` argument breaks
  practically every call to the runner.

  [^2]: This is complementary to the removal of the `mix_stderr`
  argument: the mixed output is now always stored in the `output`
  attribute, and the `stdout` is the true standard output.  Of course,
  this contradicts the previous use of `output` and `stdout`, where
  `output` was the true standard output, and `stdout` was a convenience
  alias via an extra layer of redirection.
</pre>

Merge topic branch 'translation-de' into master

2025-03-17T07:39:12+01:00

* translation-de:
  Purge hatch-gettext build plugin, and manually compile translations
  Add a German translation
  Fix indentation handling in the translation template
  Fix miscellaneous issues with the CLI messages
  Update translations template
</pre>

Purge hatch-gettext build plugin, and manually compile translations

2025-03-16T23:59:30+01:00

The hatch-gettext plugin requires Python 3.10 or higher, and
consequently hinders non-wheel installation of derivepassphrase on
Python 3.9 or PyPy 3.9.  The project also is, upon closer inspection,
alpha or beta quality: there are no tests, there appear to be no active
users (no issues or non-author pull requests filed), and the code
contains some dubious constructs (such as assembling all calls to
external programs as command-line strings, then naively splitting them
on whitespace).  I do not want to commit to using this build plugin in
any non-prototype setting.  So remove these settings from the build
system, build the translation message catalogs ourselves, and unignore
the respective paths.
</pre>

Add a German translation

2025-03-16T23:53:16+01:00

Co-authored-by: Isabell Hoffstadt
</pre>

Fix indentation handling in the translation template

2025-03-16T23:50:53+01:00

</pre>