Recent commits to derivepassphrase.git (7a4f215faf88345111135676203f9e7373e2ea98)

Test config merging with partial service configs too

2024-12-12T11:59:47+01:00

Using larger numbers of settings (and services) leads to a very low
probability of actually finding a viable path of action in the state
machine; the run is a no-op, save for the initial setup.  Presumably, we
need a larger pool of readily-assembled and/or more cross-compatible
objects, instead of the stepwise approach employed here with service
names, settings, and configurations.  This needs to be addressed in
a future commit, however.
</pre>

Merge topic branch 'pageant082' into master

2024-12-09T11:36:00+01:00

* t/pageant082:
  Explicitly support Pageant 0.82 in the test suite

GitHub: Closes #14.
</pre>

Explicitly support Pageant 0.82 in the test suite

2024-12-09T11:30:59+01:00

Pageant 0.82, released two weeks ago, supports both proper output buffer
flushing and a "foreground" mode.  Foreground mode is used to correctly
isolate a spawned Pageant instance in the test suite.  The test for
Pageant's suitability can now be simplified to whether it is at least
version 0.82, or not.

Furthermore, because no published version of Pageant supports only
proper output buffer flushing but not foreground mode, it is no longer
necessary to arrange for debug output to be silently discarded.  This
further simplifies SSH agent handling considerably.

Finally, we fix various mistakes in the documentation of the testing
machinery.
</pre>

Clean up "docs" hatch environment, also subsuming "release"

2024-12-08T19:06:33+01:00

</pre>

Merge topic branch 'logging' into master

2024-12-08T19:03:08+01:00

* t/logging:
  Document the switch to the logging and warning systems in the changelog
</pre>

Document the switch to the logging and warning systems in the changelog

2024-12-08T19:02:03+01:00

</pre>

Refactor code to run under Python 3.9's LL(1) parser

2024-12-08T17:44:25+01:00

Though it does not do so by default, Python 3.9 can run with the old
LL(1) parser instead of the PEG-based parser.  Most importantly, the
LL(1) parser does not support parenthesized context manager expressions,
and this is why they have only become officially supported in Python
3.10, once the PEG-based parser became mandatory.  Therefore, for
compatibility, we replace every "proper" parenthesized context manager
expression with equivalent explicit use of a `contextlib.ExitStack`, and
every degenerate such expression by removing the parentheses.

We now also explicitly test `derivepassphrase` with the LL(1) parser,
for as long as Python 3.9 remains supported.

While the use of a `contextlib.ExitStack` comes with additional runtime
cost, by a lucky coincidence, all such proper usage of parenthesized
context manager expressions is confined to the test suite, where we
really don't care too much about slightly higher runtimes if it buys us
more clarity, correctness and compatibility instead.
</pre>

Merge topic branch 'logging' into master

2024-12-08T12:36:36+01:00

* t/logging:
  Adapt the test suite to use the logging system properly
  Emit new info messages and better debug messages in the exporter modules
  Use the logging system to emit warnings and error messages
  Shift option parsing and grouping machinery to a separate section
  Reimplement deprecated subcommands, properly, in `click`
</pre>

Adapt the test suite to use the logging system properly

2024-12-07T09:30:38+01:00

Given the previous changes to warning and error reporting, the test
suite needs new helper code to deal with them.  Again, the changes to
mosts tests are straight-forward (the location and formatting of
messages changes slightly), but the new logging machinery itself now
also needs to be tested... particularly the code that hooks into
Python's logging system, into Python's warning system, and between those
two.

`pytest` actually includes test fixtures to capture and interact with
warnings and logging calls, but these work on the library level:
warnings are captured as warnings, logging calls are captured as log
records.  To be useful to application testing, it is necessary to
inspect and assert both the low-level warnings/log records as well as
the standard error output they ultimately translate to.  The
`hypothesis`-based tests need particular (manual) care, because
`hypothesis` rejects tests using function-scoped `pytest` fixtures.
</pre>

Emit new info messages and better debug messages in the exporter modules

2024-12-07T09:30:38+01:00

</pre>