* Guðjón Guðjónsson , 2010-12-19, 16:59:
However, what you could (and should) do is to stop harcoding Python
version in the source package, and always link qtiplot with the
default-at-build-time version of Python. That will save you (and
people who look after transitions[0]) busy work by the ne
Hi Jakub
Thanks for the answer
>
> However, what you could (and should) do is to stop harcoding Python version
> in the source package, and always link qtiplot with the
> default-at-build-time version of Python. That will save you (and people who
> look after transitions[0]) busy work by the n
* Guðjón Guðjónsson , 2010-12-04, 13:44:
Here is a question that I should know (and I think I know) the answer to
but I want to be sure :)
I am working on a new version of qtiplot and currently I hardcode python
version 2.6 for the python support.
$ ldd /usr/bin/qtiplot
...
libpython2.6
Hi again
Perhaps may earlier mail was a bit cryptic, excuse me. So I will make
another attempt to
explain my problem in the hope of an answer.
Qtiplot[1] is a fairly large program, written in C++ that contains
support for python scripting.
The python scripting part is written in sip and it
Hi
Here is a question that I should know (and I think I know) the answer to
but I want to be sure :)
I am working on a new version of qtiplot and currently I hardcode python
version 2.6 for the python support.
$ ldd /usr/bin/qtiplot
...
libpython2.6.so.1.0 => /usr/lib/libpython2.6.so.1
5 matches
Mail list logo
