Le lundi 05 mai 2008 à 11:11 +0100, martin f krafft a écrit : > also sprach Josselin Mouette <[EMAIL PROTECTED]> [2008.05.05.0905 +0100]: > > The jpilot plugin itself (in jppy-jpilot-plugins) needs to depend > > on libpython, because it has to embed the interpreter. However the > > python module (in python-jppy) should not, because it is loaded by > > the interpreter itself (even when embedded in jpilot). > > Correct me if I'm wrong, but jppy-jpilot-plugins will then depend on > python2.5 and no longer work with python2.4, right?
It will depend on python2.5 to get the interpreter, yes, but that still works if 2.4 is the system default. It’s just like a script with a #!/usr/bin/python2.5 shebang. This might cause some trouble only if some other jpilot plugins use another python version. If this is the case, jpilot needs to have a python plugin infrastructure (like epiphany or gedit) that all python plugins use. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
