Recent commits to derivepassphrase.git (845f9e01f6423c9ff612d87f0149fa448c5478ee)

Merge topic branch 'embedded-wishlist' into master

2025-06-09T22:40:12+02:00

* embedded-wishlist:
  Fix outdated MkDocs settings and dead outbound links
  Reserve the "jvm" local version identifier
  Embed our "wishlist" branch in the documentation
</pre>

Fix outdated MkDocs settings and dead outbound links

2025-06-02T22:08:35+02:00

</pre>

Reserve the "jvm" local version identifier

2025-06-01T23:11:11+02:00

Reserve the "jvm" local version identifier for `derivepassphrase-jvm`,
an early-stage port of `derivepassphrase` to the Java Virtual Machine.

(We reserve the identifier "jvm" instead of "java" because it is not yet
final whether the port will continue to be written in Java, or rather in
a different language targeting the JVM.)
</pre>

Embed our "wishlist" branch in the documentation

2025-06-01T23:05:23+02:00

The contents of `docs/wishlist/` now host a checkout of the `wishlist`
branch, providing our own bug and wish listing. The navigation includes
a new section "Wishlist", and the section includes custom CSS styling.
The "actions" partial template is also updated so that it generates
correct links to the raw file on GitHub, i.e., on the "wishlist" branch
instead of on the "master" branch.
</pre>

Merge topic branch 'click-821-prompt-testing' into master

2025-05-29T23:04:56+02:00

* click-821-prompt-testing:
  Mitigate testing discrepancies from click 8.2.0 and below
</pre>

Mitigate testing discrepancies from click 8.2.0 and below

2025-05-29T23:02:50+02:00

A discrepancy exists between the documentation of `click.prompt` and the
actual behavior of `click.prompt` when mocked with
`click.testing.CliRunner` on click 8.2.0 and below
([`pallets/click#2934`][BUG2934]): when prompting for input and if at
end-of-file, the `CliRunner` may return an empty string instead of
raising `click.Abort`. This usually translates to extra line breaks in
the "mixed" and "echoed" runner output at the last prompt(s).

We mitigate this discrepancy from both sides. On the code side, we wrap
each call to `click.prompt` to treat aborts and empty responses the
same, which is appropriate behavior for the types of prompts we issue.
On the test side, we amend our existing tests to use empty-line input
instead of no input, and explicitly test the "no input" scenario
separately, accepting both the 8.2.0-or-lower or the 8.2.1-or-higher
output. Because the behavior depends on the `click` version, which is
beyond our control, we also adjust coverage measurement.

[BUG2934]: https://github.com/pallets/click/issues/2934
</pre>

Merge topic branch 'the-annoying-os' into master

2025-05-23T00:03:24+02:00

* the-annoying-os:
  Exclude unused test function xfail_on_the_annoying_os from coverage
  Document the changes due to The Annoying OS in the changelog
  Add changes necessary to appease The Annoying OS
</pre>

Exclude unused test function xfail_on_the_annoying_os from coverage

2025-05-23T00:01:28+02:00

</pre>

Document the changes due to The Annoying OS in the changelog

2025-05-22T23:16:25+02:00

</pre>

Add changes necessary to appease The Annoying OS

2025-05-22T23:14:58+02:00

Add the changes that are necessary to appease The Annoying Operating
System, a.k.a. Microsoft Windows.

Some of these changes are OS-specific and (mostly) sensible, such as
error codes being slightly different, or some functionality not being
available.  Some of these changes are coincidental, such as linting
or type checking errors because unavailable symbols aren't even defined
for the type checker's benefit.  Finally, some changes are outright
stupid, such as Python's documentation on `tempfile.gettempdir` being
incomplete.

In the end, most changes boil down to checking for a range of error
codes instead of a specific one, or adding missing fixture calls, or
silencing type checker warnings that aren't encountered in practice, or
ruling out bad degenerate hypothesis test cases that aren't degenerate
or aren't functional at all on The Annoying OS.
</pre>