On Tue, Dec 23, 2014 at 1:07 AM, Jérémie Courrèges-Anglas <[email protected]> wrote: > viq <[email protected]> writes: > >> So, currently we have security/py-gnupg, which is >> http://py-gnupg.sourceforge.net/ and >> https://pypi.python.org/pypi/GnuPGInterface/ > > Yup. > >> Now I'm looking into porting >> https://pypi.python.org/pypi/python-gnupg/ and I have no idea how it >> should be named... Unless current one was renamed to >> py-gnupgpinterface or similiar and the new one took it's place. > > The current py-gnupg port could go away. It isn't used by any port, not > even duplicity. Rather than importing python-gnupg under a different > name, I propose a replacement. Yes the API is different, but I don't > think this is a concern. > > Here's a diff that: > - drops duplicity's dep on GnuPGInterface (it includes its own, improved > copy). > - replaces GnuPGInterface-0.3.2 with python-gnupg-0.3.7. DESCR stolen > from viq, the test that fails is due to files missing in the tarball. > > ok?
If you're asking me, then yes, certainly. Though I assume you're not, in which case - bump. -- viq
