Re: Kupfer and python3

[Ulrik Sverdrup <ulrik sverdrup gmail com>]

2010/11/2 Grigory Javadyan <grigoryj ovi com>:
> Today I found out that now the default version of python in Arch Linux is 3. Kupfer doesn't seem to work with this version. I resolved the issue by downgrading to python2 - but that's just a temporary measure, I'm sure somebody will have to port Kupfer to python 3 some day.
> Is it possible to somehow patch Kupfer so that it works correctly with both Python versions?
>

Hi,

This is the first time I hear about this. That is indeed a very bold
step to make for Arch and I think it is wrong too (python should be
python2), but it is *not* hard to compensate in Kupfer, you just have
to configure Kupfer this way:

PYTHON=python2 ./waf configure [more options here]

This is nothing strange -- you simply have to specify the python
binary to use if it's not found automatically. If it doesn't work this
way, then it's a bug.

When you ask for a Kupfer version that works with both Python 3 and
Python 2 I don't think you know how much you are asking. I will tell
you: A lot! It may never be possible to support both from the same
tarball, and porting to Python 3 will take some effort. It's not that
I haven't thought about it before (I try to write modern Python and
use Python 2.6 features that help Py3-porting), but it's not only our
Python code -- All support libraries have to be ported too. For this I
give you this list that is probably incomplete: We need Python 3 ports
of PyGTK and PyGObject/GIO, python-keybinder, dbus, wnck, and then add
modules used by plugins, like gdata for google APIs etc.

Ulrik