Thanks.
Here's what I found...
In send(), after this code fragment:
c = core.Context()
c.set_armor(1)
c.signers_clear()
for sigkey in c.op_keylist_all(sender, 1):
...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?
On Thursday, 30 January 2014 23:39:42 UTC-5, Jonathan Lundell wrote:
>
> On 30 Jan 2014, at 8:16 PM, horridohobbyist
> <[email protected]<javascript:>>
> wrote:
>
> Whoops, I goofed! I didn't realize that Python is interpreted into byte
> code files (.pyc). So the changes I made in tools.py didn't actually get
> run. I don't know how to convert tools.py into .pyc.
>
>
> Just restart web2py, and then check that the modified date of the .pyc is
> later than the .py. If you're unsure, delete the .pyc before you restart.
>
>
> On Thursday, 30 January 2014 15:36:24 UTC-5, horridohobbyist wrote:
>>
>> As a web2py newbie, I shouldn't be tinkering with foundation source code,
>> but I tried forcing the key entry to be added at line 497 of
>> gluon/tools.py. Made no difference–I'm still getting "No key for signing [
>> [email protected] <javascript:>]".
>>
>
>
>
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
