Quote:
Originally Posted by KevinH
Hi philja,
The testplugin.zip requires Python 3.4 or later. The flghtcrew plugin runs on either Python 2.7 or python 3. My guess is you have only set the path to the python 2.7 interpreter.
KevinH
|
Hi Kevin :
No ... I did use auto and it found /usr/bin/python3 and so I used the SET button and found and set to /usr/bin/python3.4 I didn't set anything at all on the top line for python2.
I have repeated this this morning and same result. Sigil treats the testplugin_v010.zip as "Error: Plugin not a valid Sigil plugin."
I downloaded the testplugin_v010.zip file a second time in case it had been corrupted. But sigil always rejects it.
I still cannot reconcile the instruction in Step 5 in the testing para of document BuildingOnLinux.md which refers to Plugins->Manage Plugins ->Edit to what I see in PluginManager. I don't see any edit option in the ManagePlugins dialogue. I don't see it in either 0.8.6 or 0.9.0 so there must be a misunderstanding somewhere.
Thanks for the explanation of where sigil is going and why Sanitycheck replaces Flightcrew on 0.9.0 as a response to F7. Flightcrew works fine even if it is slightly longer process to get it into action.
The same Building Sigil on linux document also refers to a lot of "standard" modules (besides six and lxml) that ship with binary windows versions to make use of plugins.
I can't find anything about plugins in the user manual. Can you point me to where I find information about what plugins are available ?
Thanks.