[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#660842: ITP: python-gnupg -- python wrapper for the gnupg command

On Mon, Feb 27, 2012 at 09:06:51AM +0100, Elena ``of Valhalla'' wrote:
> On 2012-02-26 at 00:26:14 +0100, Evgeni Golov wrote:
> > What's wrong with [...]
> > What are the benefits of python-gnupg? The homepage doesnt tell any,
> > neither does the description :)
> Mostly the documentation: python-gnupg's interface is fully documented 
> with docstrings (with examples checked in the test suite) and 
> it has an in-depth manual/tutorial[1].
> among the other python interfaces to gnupg functionality, 
> python-gnupginterface seems to be the one documented best 
> in the module, but the last release was in 2002 and the 
> homepage[2] features broken links both to the mailing list 
> and documentation.
> The docstrings for both python-gpgme and python-pyme are 
> both poor, and in the case of pyme the homepage just refers 
> to the pgpme docs, which are complete, but of course based on the 
> slighty different conventions of the C library.

Hm, okay.
I must admit I have used both pyme and pygpgme with great success, but 
relying on the gpgme docs, as these are quite complete and apply quite 
well to the Python versions.

Another question I would like to raise is the performance -- 
python-gnupg seems to be a command line wrapper around gnupg, thus 
having to fork() heavily -- does it affect processing of data?


Bruce Schneier can read and understand Perl programs.

Reply to: