Greg Ewing wrote: > Christian Tismer <tismer at stackless.com>: > > >>Now, any bytecode that is not yet verified can be run through >>decompyle just once, and the result is compiled again, signed >>with your key, and stored. > > > If you're going to all that bother, why not just send > suitably-signed source code in the first place? Because I prefer suitably-signed bytecode, which would usually only need the key verification, but no compile step. There is also no redundancy due to formatting. A program with a specific key always *is* that program. I always thought that with a little addition, Python source code could be completely replaced by bytecode. ciao - chris -- Christian Tismer :^) <mailto:tismer at stackless.com> Mission Impossible 5oftware : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4