Well, given the state of disarray that this matter is in, I'd best cut my losses and abandon PGP email altogether. I can't wait forever for this matter to be resolved/fixed.
Meanwhile, perhaps the web2py book should be updated to reflect the current lack of usability of PGP email, so that others like myself do not waste any more time on it. The worst thing that *official* documentation can do is to mislead the reader. Thanks. On Friday, 31 January 2014 17:25:34 UTC-5, Alan Etkin wrote: > > > >> ...the for loop is never entered. In other words, c.op_keylist_all(sender, >> 1) is empty, so c.signers_add(sigkey) is never executed. >> > >> Does that help? >> > > Not much, but at least we now know that pyme (the python wrapper for the > pgp library) cannot find any sub-key for sender, where it should. > > I'd open an issue at code.google.com/p/web2py with a link to this thread. > > BTW: pyme seems to be abandoned, there is an updated fork that is > currently maintained: > > https://bitbucket.org/malb/pyme > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
