diff --git a/.github/workflows/pythonpackage.yml b/.github/workflows/pythonpackage.yml index 662823c..400786e 100644 --- a/.github/workflows/pythonpackage.yml +++ b/.github/workflows/pythonpackage.yml @@ -32,3 +32,5 @@ jobs: - name: Test with pytest run: | coverage run -m pytest tests/test_tiny_gnupg.py + coverage report + diff --git a/CHANGES.rst b/CHANGES.rst index d4d0b2e..8658f7f 100644 --- a/CHANGES.rst +++ b/CHANGES.rst @@ -24,11 +24,6 @@ make a network connection. And in case the bug ever gets fixed (it won’t), or by accident the options do work in the future, then a tor SOCKSv5 connection will be used instead of a raw connection. -- Because of Ubuntu `bug #847388`_, Debian `bug #913614`_, & Docker - Issues [1_][2_][3_], building a GnuPG centered package using Github - actions is a deep cluster of f*cks. This means, for the moment, we - don't know which Python versions or Linux distros actually work & - build successfully. - This program may only be reliably compatible with keys that are also created with this program. That’s because our terminal parsing is reliant on specific metadata to be similar across all encountered @@ -54,11 +49,8 @@ .. _keys.openpgp.org: https://keys.openpgp.org/ .. _bug #T3065: https://dev.gnupg.org/T3065#111023 .. _bug #1788190: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1788190 -.. _bug #847388: https://bugs.launchpad.net/bzr/+bug/847388 -.. _bug #913614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614 -.. _1: https://github.com/docker-library/official-images/issues/4252 -.. _2: https://github.com/blacktangent/docker-images/issues/4 -.. _3: https://github.com/nodejs/docker-node/issues/922 + + ``Changelog`` @@ -74,6 +66,8 @@ Minor Changes - Added to Known Issues. Our package can't build on Github (Or most any CI service) for many reasons related their build environments using Docker & an issue in GnuPG itself. +- Removed Above known issue as a fix was found for using the Github CI + tool. - Added ``_home``, ``_executable``, & ``_options`` attributes which store the ``pathlib.Path.absolute()`` representation of the associated files & directories. @@ -89,9 +83,9 @@ Major Changes a substantial, possibly complete, reduction in the amount of noise gpg2 prints to the screen. Some of that printed information is helpful to see, though. We would add it back in places where it could be informative, - but passing ``"--no-tty"`` has the added benefit of potentially causing - Docker not to break right out of the gate of a build test. More thought - on this is required. + but passing ``"--no-tty"`` has the added benefit of allowing Docker not + to break right out of the gate of a build test. More thought on this + is required. - Removed ``pathlib`` from imports. That module has been in the standard library since c-python3.4. This package isn't looking to be supported for anything older than 3.6. diff --git a/PREADME.rst b/PREADME.rst index 3d23d61..c11692d 100644 --- a/PREADME.rst +++ b/PREADME.rst @@ -25,6 +25,8 @@ to change. Contributions are welcome. .. image:: https://raw.githubusercontent.com/rmlibre/tiny_gnupg/master/tests/coverage.svg?sanitize=true :target: https://raw.githubusercontent.com/rmlibre/tiny_gnupg/master/tests/coverage.svg?sanitize=true +.. image:: https://github.com/rmlibre/tiny_gnupg/workflows/Python%20package/badge.svg + :target: https://github.com/rmlibre/tiny_gnupg/workflows/Python%20package/badge.svg diff --git a/README.rst b/README.rst index a38ce94..3977c2c 100644 --- a/README.rst +++ b/README.rst @@ -25,6 +25,8 @@ to change. Contributions are welcome. .. image:: https://raw.githubusercontent.com/rmlibre/tiny_gnupg/master/tests/coverage.svg?sanitize=true :target: https://raw.githubusercontent.com/rmlibre/tiny_gnupg/master/tests/coverage.svg?sanitize=true +.. image:: https://github.com/rmlibre/tiny_gnupg/workflows/Python%20package/badge.svg + :target: https://github.com/rmlibre/tiny_gnupg/workflows/Python%20package/badge.svg @@ -332,11 +334,6 @@ After a user no longer considers a key useful, or wants to dissociate from the k make a network connection. And in case the bug ever gets fixed (it won’t), or by accident the options do work in the future, then a tor SOCKSv5 connection will be used instead of a raw connection. -- Because of Ubuntu `bug #847388`_, Debian `bug #913614`_, & Docker - Issues [1_][2_][3_], building a GnuPG centered package using Github - actions is a deep cluster of f*cks. This means, for the moment, we - don't know which Python versions or Linux distros actually work & - build successfully. - This program may only be reliably compatible with keys that are also created with this program. That’s because our terminal parsing is reliant on specific metadata to be similar across all encountered @@ -362,11 +359,8 @@ After a user no longer considers a key useful, or wants to dissociate from the k .. _keys.openpgp.org: https://keys.openpgp.org/ .. _bug #T3065: https://dev.gnupg.org/T3065#111023 .. _bug #1788190: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1788190 -.. _bug #847388: https://bugs.launchpad.net/bzr/+bug/847388 -.. _bug #913614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614 -.. _1: https://github.com/docker-library/official-images/issues/4252 -.. _2: https://github.com/blacktangent/docker-images/issues/4 -.. _3: https://github.com/nodejs/docker-node/issues/922 + + ``Changelog`` @@ -382,6 +376,8 @@ Minor Changes - Added to Known Issues. Our package can't build on Github (Or most any CI service) for many reasons related their build environments using Docker & an issue in GnuPG itself. +- Removed Above known issue as a fix was found for using the Github CI + tool. - Added ``_home``, ``_executable``, & ``_options`` attributes which store the ``pathlib.Path.absolute()`` representation of the associated files & directories. @@ -397,9 +393,12 @@ Major Changes a substantial, possibly complete, reduction in the amount of noise gpg2 prints to the screen. Some of that printed information is helpful to see, though. We would add it back in places where it could be informative, - but passing ``"--no-tty"`` has the added benefit of potentially causing - Docker not to break right out of the gate of a build test. More thought - on this is required. + but passing ``"--no-tty"`` has the added benefit of allowing Docker not + to break right out of the gate of a build test. More thought on this + is required. +- Removed ``pathlib`` from imports. That module has been in the standard + library since c-python3.4. This package isn't looking to be supported + for anything older than 3.6. diff --git a/tiny_gnupg.egg-info/PKG-INFO b/tiny_gnupg.egg-info/PKG-INFO index 67bf728..e96624a 100644 --- a/tiny_gnupg.egg-info/PKG-INFO +++ b/tiny_gnupg.egg-info/PKG-INFO @@ -35,6 +35,8 @@ Description: tiny_gnupg - A small-as-possible solution for handling GnuPG ed2551 .. image:: https://raw.githubusercontent.com/rmlibre/tiny_gnupg/master/tests/coverage.svg?sanitize=true :target: https://raw.githubusercontent.com/rmlibre/tiny_gnupg/master/tests/coverage.svg?sanitize=true + .. image:: https://github.com/rmlibre/tiny_gnupg/workflows/Python%20package/badge.svg + :target: https://github.com/rmlibre/tiny_gnupg/workflows/Python%20package/badge.svg @@ -342,11 +344,6 @@ Description: tiny_gnupg - A small-as-possible solution for handling GnuPG ed2551 make a network connection. And in case the bug ever gets fixed (it won’t), or by accident the options do work in the future, then a tor SOCKSv5 connection will be used instead of a raw connection. - - Because of Ubuntu `bug #847388`_, Debian `bug #913614`_, & Docker - Issues [1_][2_][3_], building a GnuPG centered package using Github - actions is a deep cluster of f*cks. This means, for the moment, we - don't know which Python versions or Linux distros actually work & - build successfully. - This program may only be reliably compatible with keys that are also created with this program. That’s because our terminal parsing is reliant on specific metadata to be similar across all encountered @@ -372,11 +369,6 @@ Description: tiny_gnupg - A small-as-possible solution for handling GnuPG ed2551 .. _keys.openpgp.org: https://keys.openpgp.org/ .. _bug #T3065: https://dev.gnupg.org/T3065#111023 .. _bug #1788190: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1788190 - .. _bug #847388: https://bugs.launchpad.net/bzr/+bug/847388 - .. _bug #913614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614 - .. _1: https://github.com/docker-library/official-images/issues/4252 - .. _2: https://github.com/blacktangent/docker-images/issues/4 - .. _3: https://github.com/nodejs/docker-node/issues/922 @@ -394,6 +386,8 @@ Description: tiny_gnupg - A small-as-possible solution for handling GnuPG ed2551 - Added to Known Issues. Our package can't build on Github (Or most any CI service) for many reasons related their build environments using Docker & an issue in GnuPG itself. + - Removed Above known issue as a fix was found for using the Github CI + tool. - Added ``_home``, ``_executable``, & ``_options`` attributes which store the ``pathlib.Path.absolute()`` representation of the associated files & directories. @@ -409,9 +403,12 @@ Description: tiny_gnupg - A small-as-possible solution for handling GnuPG ed2551 a substantial, possibly complete, reduction in the amount of noise gpg2 prints to the screen. Some of that printed information is helpful to see, though. We would add it back in places where it could be informative, - but passing ``"--no-tty"`` has the added benefit of potentially causing - Docker not to break right out of the gate of a build test. More thought - on this is required. + but passing ``"--no-tty"`` has the added benefit of allowing Docker not + to break right out of the gate of a build test. More thought on this + is required. + - Removed ``pathlib`` from imports. That module has been in the standard + library since c-python3.4. This package isn't looking to be supported + for anything older than 3.6. @@ -461,6 +458,7 @@ Description: tiny_gnupg - A small-as-possible solution for handling GnuPG ed2551 the in decript ``CalledProcessError``. Exceptions currently being used include: ``LookupError``, ``PermissionError``, ``TypeError``, ``ValueError``, ``KeyError``, & ``FileNotFoundError``. + - ``ValueError`` raised in ``text_export()`` & ``sign()`` switched to ``TypeError`` as it's only raised when their ``secret`` or ``key`` kwargs, respectively, are not of type ``bool``.