Recent commits to derivepassphrase.git (760cca228aa3b8f8b6e6610d0334f4b744d4d19f)

Fix Zsh completion output, again

2025-01-17T20:51:03+01:00

The new Zsh serialization handler in
bba4bd075ab5e1d6a6a76d90b129ad0d58425b96 was tested only against
completion items with descriptions, and it did not properly take into
account that items *without* descriptions would be passed directly to
Zsh as unescaped completion entries, i.e., no interpretation of escape
sequences would occur.  We fix this in both the code and the tests, and
include a safeguard against applying this against the wrong Zsh
completion script version (at least as far as we can programmatically
determine from within Python).

References: [click#2703](https://github.com/pallets/click/issues/2703)
</pre>

Merge topic branch 'usage-fixes' into master

2025-01-16T01:52:47+01:00

* t/usage-fixes:
  Add changelog entry for the recent renaming and recasting of some type
  Fix usage of `mypy --python-version=3.9` and friends
  Make key pairs, key sets and key-comment pairs generic
  Convert `tests.SSHTestKey` into a named tuple
  Move storeroom helper types into `_types` module, as named tuples
  Fix formatting and linting issues
</pre>

Add changelog entry for the recent renaming and recasting of some type

2025-01-16T01:50:18+01:00

</pre>

Fix usage of `mypy --python-version=3.9` and friends

2025-01-16T01:28:57+01:00

On the one hand, use a small stub file for `tomli`, because `mypy` is
run from all sorts of `hatch` environments or Python virtual
environments that are not set up correctly with `tomli`.

On the other hand, type checking cannot rely on
`try`-`except`-`ImportError` blocks working for type inference purposes,
so variables imported as such need an explicit declaration.  (In this
specific case, this could be alleviated with explicit Python version
checks, but I find that decidedly unpythonic.)
</pre>

Make key pairs, key sets and key-comment pairs generic

2025-01-16T01:05:38+01:00

Parametrize `_types.SSHKeyCommentPair`, `_types.StoreroomKeyPair` and
`_types.StoreroomMasterKeys` over the exact `Buffer` type being used.
Also supply a `.toreadonly()` method (similar to
`memoryview.toreadonly()`) that converts all `Buffer`s to `bytes`
objects.
</pre>

Convert `tests.SSHTestKey` into a named tuple

2025-01-16T00:55:16+01:00

Again, this makes the notation more readable, and allows test keys to
contain methods.  Use this to group keys into always suitable keys and
other keys, instead of having to manually define appropriate tables.
</pre>

Move storeroom helper types into `_types` module, as named tuples

2025-01-15T21:07:32+01:00

Move `exporter.storeroom.KeyPair` and `exporter.storeroom.MasterKeys`
into the `_types` module, as `StoreroomKeyPair` and
`StoreroomMasterKeys`, respectively.  Also convert them from `TypedDict`
to `NamedTuple`.

Also rename `_types.KeyCommentPair` to `_types.SSHKeyCommentPair` for
consistency.
</pre>

Fix formatting and linting issues

2025-01-15T20:09:20+01:00

</pre>

Merge topic branch 'l10n-machinery' into master

2025-01-15T19:31:19+01:00

* t/l10n-machinery:
  Convert translatable string construction in enums to positional args only
  Normalize and unwrap translatable strings (messages and comments)
  Add hypothesis-based tests for l10n machinery
  Fix obvious coverage failures among the translatable strings machinery
  Split off comments in translatable string enum value constructor
  Sort arguments to translatable string enum value constructor
  Issue new context IDs for translatable messages
  Fix debug output of messages with trimmed filenames
  Support SOURCE_DATE_EPOCH for .po file generation
  Move translation string preparation into the TranslatableString class
  Properly support trimmed filenames in translation strings
  Generate debug translations automatically, in code and on the command-line
  Hide translation template enums behind a type alias
</pre>

Convert translatable string construction in enums to positional args only

2025-01-15T19:23:47+01:00

This too makes the rendered code more readable by elliding repetitive
information.
</pre>