Re: Kupfer and python3

[Martin Koelewijn <martinkoelewijn gmail com>]

Hi all,

as an arch user I was surprised to see python3 being implemented like
this. Not that I care very much. It was documented and made known quite
well. And you can have python (version 3) and python2 both installed of
course. 
The workaround (PYTHON=python2) is very useful. Maybe it can be added
on the site or in the README at install instructions? Btw the AUR
package has this already and should be preferred to install kupfer
above the tarball. I don't think it's up to kupfer to switch to python3
ASAP just because a bleeding edge distro did (although it is the most
awesome ;) ). It's not just an upgrade, it's a total new beast, and
supporting libraries need to be upgraded too, like Ulrik explained. 
Just my 2 cents. 

Martin

On Tue, 2 Nov 2010 22:30:04 +0100
Ulrik Sverdrup <ulrik sverdrup gmail com> wrote:

> 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
> _______________________________________________
> kupfer-list mailing list
> kupfer-list gnome org
> http://mail.gnome.org/mailman/listinfo/kupfer-list