Well, I can't really verify this, I do think putting this into
script.cpp so that it'll check the "locally installed" version before
looking to the system installed one is a good way to go. I suggested
this earlier but no one would tell me how to do that on Windows ;) It
looks like this would work for Perl and Ruby also, if we decide to
ship those in the future, is that true?
I guess that makes sense. For all three interpreters, use the
we supply, over the one specified in the path. So how about this order of
1) Use the one specified in the prefs, (defaults to none)....
2) Use the location of inkscape.exe to hardcode the interpreter's
relative to it. If it doesn't exist.....
3) Search the PATH (what is currently happening).
This will still allow the end user to specify which python.exe he wants,
if he is designing a new Effect.
We still really ought to launch the local copy via C, but we're way
too close to the release for that.