-
Notifications
You must be signed in to change notification settings - Fork 156
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
Live reload of the Python code #86
Comments
While at this, also investigate remote debugger viability. At first glance, it might work |
Just noticed this snippet from https://www.jython.org/jython-old-sites/docs/library/zipimport.html:
So, maybe we need to 1) enable debug setting; 2) reload extension; 3) upon reload detect debug setting and change |
Add the liver reload functionality for the development. This should only affect Python code.
Implementation, roughly: add setting to enable live reload with a requirement to specify directory on the file system to use, instead of JAR file. Shuffle
sys.path_hooks
(as mentioned in Jython docs) to prioritize file system over JAR. Add a button "Reload InQL" that is only shown when debugging is enabled in the settings. On click issue Python 2'sreload()
command for each module (not sure whether this has to be every import statement? how do we track them?).This only makes sense after the core functionality (like temporary directory creation) gets moved to Kotlin as we should tear down all UI elements & stop Python threads & recreate them after reload.
The text was updated successfully, but these errors were encountered: