>>> import __main__ as m # I know, not general, just for trial >>> m.c=3 Isn't (in 3.0) the notion of being able to modify another module's globals supposed to get restricted to help out (among other things) the compiler? If so, this use, even though it's not really modifying a global in another module, might not work forever. 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