https://git.schokokeks.org/derivepassphrase.git/tree/af0cd7e9e4b0c823bf1385d6942ef7ba44f53649Recent commits to derivepassphrase.git (af0cd7e9e4b0c823bf1385d6942ef7ba44f53649)2025-01-29T22:30:02+01:00tag:gitlist.org,2012:commit/af0cd7e9e4b0c823bf1385d6942ef7ba44f53649Merge topic branch 'split-cli-module' into master2025-01-29T22:30:02+01:00Marco Riccisoftware@the13thletter.info
<pre>* t/split-cli-module:
Document the trimming of the `cli` module in the changelog
Split off cli_helpers and cli_machinery internal modules
Move CLI messages module into a new `_internals` subpackage
</pre>
tag:gitlist.org,2012:commit/aa0968564bd32aff89877e91cea4da237998aeaeDocument the trimming of the `cli` module in the changelog2025-01-29T22:29:01+01:00Marco Riccisoftware@the13thletter.info
<pre></pre>
tag:gitlist.org,2012:commit/623f749ed8245822f7b00520bd4096d008673685Split off cli_helpers and cli_machinery internal modules2025-01-29T22:23:26+01:00Marco Riccisoftware@the13thletter.info
<pre>Split off the `logging` and `click` support code (the "machinery") and
the command-specific helper functions (the "helpers") into separate
modules under `derivepassphrase._internals`. Change all functions,
classes and attributes within those new modules to be public with
respect to the module, since the module itself is already non-public.
Also document all previously undocumented classes and functions:
`cli_helpers.ORIGIN`, `cli_helpers.check_for_misleading_passphrase`,
`cli_helpers.key_to_phrase` and `cli_helpers.print_config_as_sh_script`.
Add a better default value (`cli_helpers.default_error_callback`) for
the `error_callback` parameter of `cli_helpers.key_to_phrase`, and
document that too. Finally, since the shell completion parts are now
split across two modules, add an explicit TODO to the
`cli_machinery.ZshComplete` class to add context.
</pre>
tag:gitlist.org,2012:commit/733aeec69f03e5b8cfa025ee381dce10902f821cMove CLI messages module into a new `_internals` subpackage2025-01-29T20:34:40+01:00Marco Riccisoftware@the13thletter.info
<pre>Also adjust the headings in the development build of the documentation
to clearly mark internal documentation as internal.
(The absolute imports within the CLI messages module make the move
itself relatively painless: only the callers need to be adjusted to the
new path.)
</pre>
tag:gitlist.org,2012:commit/258929497c5a8582f02e6b3fe3e42fad45e1bb86Merge topic branch 'vault-module-api' into master2025-01-29T16:35:02+01:00Marco Riccisoftware@the13thletter.info
<pre>* t/vault-module-api:
Document API changes in the vault module
Adjust coverage on vault tests for error-only code paths
Adjust docstrings for vault "symbol" character class
Make the vault UUID and CHARSETS attributes public
Let `Vault` accept Buffer-type values wherever it accepts bytes
</pre>
tag:gitlist.org,2012:commit/9cca65fc7dbc704b832332abdf441745e77b85b5Document API changes in the vault module2025-01-29T16:34:22+01:00Marco Riccisoftware@the13thletter.info
<pre></pre>
tag:gitlist.org,2012:commit/a9025de171c37b4a8ba78945906e800616c1d9a3Adjust coverage on vault tests for error-only code paths2025-01-29T15:36:12+01:00Marco Riccisoftware@the13thletter.info
<pre>Code paths in the tests that only do error handling due to factors
beyond their control (here: unsatisfied hypothesis assumptions, or
re-raising the error) should not be counted towards coverage.
</pre>
tag:gitlist.org,2012:commit/45152120fe7dbcfdac8ba2786507a3bad882be53Adjust docstrings for vault "symbol" character class2025-01-29T15:33:36+01:00Marco Riccisoftware@the13thletter.info
<pre>The "dash" class is a subset of "symbol", so we can't talk about "all
hitherto unlisted ASCII printable characters", but should list the
exceptions explicitly.
</pre>
tag:gitlist.org,2012:commit/689cf84c5396b0d92909c554d5c2a75453c55c24Make the vault UUID and CHARSETS attributes public2025-01-29T15:28:07+01:00Marco Riccisoftware@the13thletter.info
<pre>They are constants, they are not priviledged information, and having to
keep indirectly referring to them instead of directly is rather
irritating.
</pre>
tag:gitlist.org,2012:commit/7dc1d96b25a124f2f599e261c168928bc375a677Let `Vault` accept Buffer-type values wherever it accepts bytes2025-01-29T15:07:21+01:00Marco Riccisoftware@the13thletter.info
<pre>Any method that accepts `bytes` and `bytearray` now also accepts
arbitrary Buffer-type classes such as `memoryview` and `array.array`.
The return values (mostly `bytes`, sometimes `bytearray`) remain
unchanged.
</pre>