-
Notifications
You must be signed in to change notification settings - Fork 77
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
Cannot use GUI because ScriptEngine not found #215
Comments
Nothing dramatic, it's enough to uncomment the 3 commented lines near here: I removed that because it messes up console output when running a python script from the terminal. I think the proper fix is to have the server create its script engine on startup, rather than doing it always on python library load. |
OK, after uncommenting those lines, I recompiled and tried again.
|
ok, unfortunately I didn't check for python availability to create the python console, I'll try to do that as soon as possible. |
I tried too, and I get a crash (sometimes server, sometimes GUI) with the following trace:
I tried getting a more detailed backtrace using the debugger, but in debug mode I get a different error from the server:
|
Can anyone give an explanation why this happens? |
Weird, I had this kind of errors a long time ago. Which version of Python are you using ? |
python 2.7 On 30 May 2012, at 16:22, vivianbolsee wrote:
|
This part of ScritEngine uses a lot of old python C code. I will rewrite this with Boost::Python today. Sorry for the wait. |
No problem Vivian, thanks for this! |
When trying to launch the GUI, and any command is executed, i get an error that the path
'/Tools/Python/ScriptEngine' is not found.
When checking in the component tree in the GUI, the component /Tools/Python does not exist.
I have python installed, compiled, ... so that is not the problem.
The python console is available as well, but any command typed in there results in the same error.
Also trying to configure any option through the GUI, results in the same error.
Anyhow, if python was not found, the python console should not appear (Can Vivian confirm?)
This bug should be fixed asap. Can Vivian do this still?
The bug is there in the latest commit (7fb47cc) of the main repo
The text was updated successfully, but these errors were encountered: