Recent commits to derivepassphrase.git (59082d1f81b629c4be67bdcce2977db289d7c3af)

Tell MkDocs to ignore scriv's changelog snippets

2024-10-04T10:55:32+02:00

The master changelog file is included, of course, but we don't want
MkDocs to bother with the single snippets (rendering them, generating
warnings that they're not part of the navigation tree, etc.).
</pre>

Update required Python version in the README

2024-10-03T13:40:52+02:00

This was forgotten while adding Python 3.9 support.
</pre>

Relax hypothesis deadline for another slow-ish test

2024-10-03T13:30:36+02:00

The vault settings validation test keeps timing out on my older
hardware, when running without the C tracer and at moderate power saving
settings.  I can only presume it would time out similarly on even
lower-powered hardware, such as a Raspberry Pi.
</pre>

Merge topic branch 'issue15-graceful-af_unix-degredation' into master

2024-10-02T20:35:24+02:00

* t/issue15-graceful-af_unix-degredation:
  Fail gracefully if UNIX domain socket support is unavailable

GitHub: Closes #15.
</pre>

Fail gracefully if UNIX domain socket support is unavailable

2024-10-02T19:26:30+02:00

To talk to the SSH agent, we currently require UNIX domain socket
support, but not every Python on every system supports this (notably:
Windows).  If we detect such missing support, fail gracefully and with
a useful error message, instead of a technical reason such as
`AttributeError`.

Besides the new failure modes that API consumers will need to handle,
this results in one more observable change: socket objects passed to the
`SSHAgentClient` constructor are now required to be already connected.
The constructor will no longer prepare sockets it didn't create itself
in any way.

This new failure behavior also has consequences for the tests, which so
far have naively assumed UNIX semantics and UNIX domain socket support.
So change the testing machinery to automatically skip any test that
involves constructing a custom SSH agent client *and* expecting that
step to go well.  Furthermore, since the "no support" constellation can
be reasonably well simulated even on systems that *do* have UNIX domain
socket support (via pytest's monkeypatching fixture), include explicit
tests on the API and the CLI level for the "no support" constellation,
in any case.
</pre>

Merge topic branch 'support-py39' into master

2024-10-02T09:32:06+02:00

* t/support-py39:
  Add changelog entry for Python 3.9 support
  Add support for Python 3.9
  Accomodate known slow tests in hypothesis deadline
  Fix awkward parametrization declaration for SSH agent client tests
</pre>

Add changelog entry for Python 3.9 support

2024-10-02T09:31:40+02:00

</pre>

Add support for Python 3.9

2024-10-01T11:51:05+02:00

Support Python 3.9 by not using the following features:

  - `match`/`case` statements; replace them with `if`-statements
  - annotation-like class unions in `isinstance`; use a tuple instead
  - `TypeAlias` objects; write these as strings
  - the `root_dir` parameter of `glob.glob`; build the file list via
    `fnmatch.fnmatch` ourselves
</pre>

Accomodate known slow tests in hypothesis deadline

2024-10-01T11:36:02+02:00

With coverage measurement enabled, program execution can slow down by
a factor of roughly 40 if the Python tracer is used, instead of the
C tracer.  In some configurations, only the Python tracer is available.
To avoid timing out on tests that otherwise would be okay with default
settings, manually reset those tests' deadline to 40 times their
original value; currently only one test is affected.
</pre>

Fix awkward parametrization declaration for SSH agent client tests

2024-10-01T10:15:36+02:00

Instead of introducing a static method, calling it to obtain test
parameters, then removing it again, use a declaration within the
`pytest.mark.parametrize` decorator arguments, even if that is
supposedly more difficult to read (I wouldn't agree).  Among the
readability benefits (primarily because of compactness), the imperative
version via a static method throws errors on Python 3.9, presumably
because the `staticmethod` object itself is being returned, not the
bound method object, and the former isn't callable in Python 3.9.

On a related note, a future import for annotations was missing as well.
</pre>