Michel Pelletier wrote: > I am also working on a short list of static and structural > constraints for > bytecode, this is what I have so far (the ones i'm unsure about are > questions): A couple gotchas when useing new.code(): 1. co_names, co_varnames, co_freevars, and co_cellvars take tuples of strings; passing unicode strings crashes the interpreter. co_consts, however, is unicode-safe. 2. Some co_flags should be checked to be consistent with other args; for example, shouldn't CO_NOFREE be set if co_freevars is empty? Robert Brewer MIS Amor Ministries fumanchu at amor.org
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