Related to ticket #1319, dylink.repy should only evaluate the imported code only once. Currently dylink caches the imported module, but still evaluates the code every time the module is imported. We should be caching the evaluated module as well and evaluate when necessary.
Related to ticket #1319, dylink.repy should only evaluate the imported code only once. Currently dylink caches the imported module, but still evaluates the code every time the module is imported. We should be caching the evaluated module as well and evaluate when necessary.