Quote:
Originally Posted by Doitsu
Of course switching to an different external Python interpreter would be the easiest solution, however, many Sigil plugin users apparently have limited technical skills and some might have difficulties installing Python.
|
I agree. But I also think those same users with limited technical skills would struggle just as mightily using pip from a command-line to install a new module.
Those who know ... likely already can; and those who don't know, will probably be just as lost with even a Sigil-centric command-line pip anyway
For what it's worth, something like this has always been on my back-burner (because I know Kevin could implement it pretty easily on Macs). But I'm thinking that for it to be useful to the most people, it almost needs to be a function that's kicked off from within Sigil itself (Install Additional Modules to Sigil's Bundled Python). Something that can be used to entirely control how the bundled pip would be launched.
Something that could conceivably be implemented now would be to have a path in a user's Sigil Preferences directory be added to Sigil's bundled Python's sys.path. Knowledgeable users could copy pure python modules there to be available to the bundled interpreter. But that doesn't seem any more advantageous to knowledgeable users to me than simply switching python interpreters.