On Nov 14, 2008, at 5:03 PM, Martin Dobias wrote:
So now the question is (and something I've wondered about) - just
how does
this python support work? Does it execute the python program (as
found in
the user's PATH)? Does it depend on linking to the python library
to find
some python start/init symbol?
We're using only direct API function calls to python C library, python
executable is _not_ being run.
To get libqgispython working properly, it's loaded from QGIS
application with following Qt's load hints:
Ugh. So, libqgispython is loaded more like a library, and it expects
the python library to be loaded somehow - by the compiler linking -
which is what we need to avoid.
I wonder if Qgis can load the python library in the same way it loads
libqgispython, so that the python symbols are available to
libqgispython when it's loaded? Then it could load whichever python
is "default", whatever that may mean, or have a Qgis preference (like
setting the GRASS location) to let the user choose a Python to use.
Otherwise, whatever is done to make all the PyQt and Qgis python
extensions "proper" won't matter, since libqgispython will be stuck
with whichever python it was compiled with.
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"This is a question about the past, is it? ... How can I tell that the
past isn't a fiction designed to account for the discrepancy between
my immediate physical sensations and my state of mind?"
- The Ruler of the Universe
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
