Quote:
Originally Posted by varlog
not sure.. will investigate... no official site with tagged releases?
|
Not sure what you mean. The official site for KindleUnpack
IS KevinH's github repository. My KindleImport plugin uses the python2and3 branch there. Which hasn't had any official tagged releases yet. I like head starts.
Quote:
|
it didn't... by 2.7 (Ubuntu14.04) tk was included, but your plugin invokes unconditionally python 3 apparently.
|
Yeah, no. My plugin does no such thing. I've tested both its python2 and python3 functionality extensively on Windows and Linux. It will work with either. I think you'll find that in Sigil's Plugin Manager, you have both the python2 and python3 interpreters configured. In the case where both interpreters are configured and available, KindleImport (not being able read human minds yet) will default to using the python3 interpreter (because it has to choose
one of them after all). If you remove the path to the python3 interpreter, it will happily use the python2 interpreter. If you'd like it to default to using python2 while leaving both interpreters configured, crack the zip open and reverse the order of the two <engine> entries in the plugin.xml file.
Quote:
On my schedule tomorrow (f..k you python, here I come again! ). My patch for Sigil works for 0.8.4 with no conflicts at the moment. The other one too . Thank you user_none/kevinH!
Will post varlogsKindleImport here when I'm through, though.
And still I want 10 points of your karma! The software should make all those dumb necessary activities more unnecessary... "dummy.epub", indeed!
|
Best of luck with all that. I'd rather you changed the plugin name a
little more than that, but whatever... do what you think best.