python-pskc branch master updated. 1.3-4-gcfaae11

[Commits of the python-pskc project <python-pskc-commits [at] lists.arthurdejong.org>]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "python-pskc".

The branch, master has been updated
       via  cfaae11c0bb4ac29ff9cf6167fd7f09be518b428 (commit)
      from  ab5bea997f08db0f1736396fd9617b15df9ba403 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://arthurdejong.org/git/python-pskc/commit/?id=cfaae11c0bb4ac29ff9cf6167fd7f09be518b428

commit cfaae11c0bb4ac29ff9cf6167fd7f09be518b428
Author: Arthur de Jong <arthur@arthurdejong.org>
Date:   Thu Feb 6 17:33:09 2025 +0100

    Spelling fixes (thanks codespell)

diff --git a/pskc/policy.py b/pskc/policy.py
index b72aca3..a66e983 100644
--- a/pskc/policy.py
+++ b/pskc/policy.py
@@ -24,7 +24,7 @@ import warnings
 
 
 def _make_aware(d):
-    """Make tge specified datetime timezone aware."""
+    """Make the specified datetime timezone aware."""
     import dateutil.tz
     if not d.tzinfo:
         return d.replace(tzinfo=dateutil.tz.tzlocal())
diff --git a/tests/test_rfc6030.doctest b/tests/test_rfc6030.doctest
index df5193b..c02c851 100644
--- a/tests/test_rfc6030.doctest
+++ b/tests/test_rfc6030.doctest
@@ -217,7 +217,7 @@ True
 
 
 This tests a PSKC file that uses asymmetric encryption as seen in figure 8 of
-RFC 6030. Note thet python-pskc does not yet support asymmetric encryption so
+RFC 6030. Note that python-pskc does not yet support asymmetric encryption so
 this test is really limited.
 
 >>> pskc = PSKC('tests/rfc6030/figure8.pskcxml')
diff --git a/tests/test_write.doctest b/tests/test_write.doctest
index c1ea198..04d1c9e 100644
--- a/tests/test_write.doctest
+++ b/tests/test_write.doctest
@@ -659,7 +659,7 @@ set on one key end up being applied to both keys.
 
 If we specify a global IV it will be used for all encrypted values but will
 be not be written as a global IV in the PSKC file because RFC 6030 does not
-specify this (and re-using an IV is a bad idea).
+specify this (and reusing an IV is a bad idea).
 
 >>> pskc = PSKC()
 >>> key = pskc.add_key(secret='1234')

-----------------------------------------------------------------------

Summary of changes:
 pskc/policy.py             | 2 +-
 tests/test_rfc6030.doctest | 2 +-
 tests/test_write.doctest   | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
python-pskc