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.
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 [ > my_han...@gmail.com]". > > Thanks. > > > On Thursday, 30 January 2014 12:45:14 UTC-5, Alan Etkin wrote: >> >> >> >>> - The key was found but the can_sign property is set to False >>> >>> but I can't find how to set it... :( >>> >> >> You mean the o.s. command to enable signing? (wathever it is)? What if >> one forces the test to True at tools.py (so the key entry is added)? The >> problem about pyme is the lack of documentation IMO. >> > -- 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.
