-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repyportability in RepyV2 should allow us to import Repy files from pythonpath #25
Comments
Author: monzum
Running the above code will allow us to locate hello.repy from pythonpath and attempt to import it. However the import will fail when hello.repy tries to import world.repy
I will keep digging into this and try to figure out why this is the case. |
Author: monzum
|
This build file is needed to set up the RepyV2 runtime which the custominstallerbuilder requires to run. We need to do that because plain Python `import`'s from Repy libraries don't currently work. Future contributors, please check if this workaround is still needed every time progress is made on SeattleTestbed/portability#25, SeattleTestbed/portability#26, SeattleTestbed/portability#27, or SeattleTestbed/portability#28!
Currently we are not able to use dy_import_module_symbols() to import repy modules into python files even if the modules are in the pythonpath. In RepyV1, repyhelper was able to translate and import all repy files into a python file as long as the repy file was in the pythonpath. It seems we lost this feature in Repy V2 when using repyportability + dylink. This feature would be very nice for projects such as AFFIX.
The text was updated successfully, but these errors were encountered: