On 2012-02-27 at 09:23:04 +0100, Evgeni Golov wrote:
> 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?
Probably yes, in cases where one is manipulating a significant
number of keys/messages in a short time.
In many other usecases where the gnupg command is used sparsely
in the program lifecyle I don't think the added overhead
is going to be relevant to the user experience.
My current usecase, for example, is a script that will verify
a signature on a message and then further process it in
a non-gpg related way: I don't feel that the runtime savings
from using a non fork()ing module would be worth
the additional developement time needed to use a module that is
more complete, more efficient but also seems to be more code-intensive
for simple tasks.
I'm changing the description with a mention of what I
believe are the strong points of python-gnupg.
Description: pythonic wrapper for the gnupg command
python-gnupg is a module that uses subprocess to wrap the gnupg
command and provide a simple and well documented
interface to basic gpg functionalities such as generating
and managing keys, encrypting and decrypting data, signing and
verifing messages.
--
Elena ``of Valhalla''
Attachment:
signature.asc
Description: Digital signature