Nikos Kouremenos wrote:
> GNUPGInterface scans output of GPG right?
>
>Pyme speaks to GPGME which does what? (apart from being "easy")
>
>
Well... The sad part is that GPGME also starts a separate GPG process
and communicates with it via pipes. It's mostly the "easy" part which
separates it from GNUPGInterface. Another difference is that both GPGME
and GNUPG are maintained by the same team which makes you hope that
communication between these 2 components will be kept in sync without
any changes to PyMe.
Plus, there's a talk of having part of GNUPG code working with the
keyrings to be moved into a separate library and then GPGME could be
rewritten using this future library directly instead of starting a
separate GPG process. Hopefully, the GPGME interface will be left the same.
As for my status of compilation under Windows - I have PyMe and GPGME
compiled under cygwin, but it makes it dependent on number of other
CygWin DLLs. I'm trying to compile GPGME with mingw now but ran into
strange problems which probably related to the communication between
GPGME and the started GPG. I'm still investigating it.
Cheers,
Igor
|
