> What about PEP 301 and an import hook? Couldn't a custom import > hook be written up that didn't output a .py file? I would think it > could be as simple as finding the file, opening it, and then > compiling it as a module and inserting it directly into > ``sys.modules``. Wouldn't that circumvent any .py(c|o) writing? I think using an import hook to prevent writing .pyc files is way too much work. You can't use the built-in code because that *does* write the .pyc files, so you have to redo all the work that the standard hook does. --Guido van Rossum (home page: http://www.python.org/~guido/)
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