Hi Jeremy, Chimera replaces os.popen with a custom version that gives the subprocess the environment that Chimera was invoked with, rather than the changed environment that Chimera starts its Python interpreter with. The extension you are using must be calling os.popen (line 259 in chimeraIniit is in the modified popen). We could help better if you could provide the entire traceback. When the extension generates the error you should be getting a report-a bug dialog. You should use that — it will send us the traceback. If you aren’t getting the dialog, then after you get the error use Help→Report A Bug to get the bug-reporting dialog, and then use it the same way. —Eric Eric Pettersen UCSF Computer Graphics Lab
On Oct 17, 2019, at 3:00 PM, Deng Chengtian <joedct.xd@gmail.com> wrote:
Hi,
I am trying to run an existing extension but it generate an error [error2] such that the file”<chimera directory>\share\chimeraInit.py,” line 259, in create process. Could you let me know what is potentially happening? The extension I dowloaded were created according to the instruction, but I don’t know if it is because a version conflict or maybe it s because it wasn’t dowloaded into a correct location? The plug-in seems successfully loaded into chimera and have its own window under tools/utilities.
Best regard, Jeremy Deng _______________________________________________ Chimera-dev mailing list Chimera-dev@cgl.ucsf.edu http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-dev