>> [ importing to scan snipped ]
>>
>> Yes, this is one of the worst problems I know of. I plan on changing
>> this.
Guido> If you don't want to give up scanning the bytecode (if that's
Guido> what you do), you could use compile() on the source code to get
Guido> the bytecode for the entire module.
I think we may need to start thinking about some standard interface to byte
code scanning. (I keep thinking about Rattlesnake.) Perhaps there are
standard tasks people are performing that could be abstracted into a
standard module (for example, getting a list of global variables that are
set by a function, or getting first set and first read points for particular
variables). One complaint I saw voiced about the Rattlesnake idea was that
code that scans byte code would break.
Skip
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