Re: Python 3.0 support

[Johan Dahlin]

Ralf Wildenhues wrote:
[..]
> > Python 3.0 changes has major backwards incompatible changes, we have to 
> > be rather careful to use a subset which works on both 2.x and 3.x.
> > The patches have been tested on Python 2.5 and 3.0. I am confident that
> > they will work on versions as early as 2.0. Support for versions
> > prior to that has been dropped (2.0 was released in 2000) and that is
> > mentioned in the NEWS file.
>
> Sounds fair to me, if support for pre-2.0 is difficult to keep.
> As I don't know python very well, can you elaborate a bit on
> why that is?

It's not really that difficult no, but there's just not a lot of sense to do 
so as it is really old. I don't expect anyone doing serious programming
against Python 1.5.2 these days where an upgrade to automake HEAD is
in any way justifiable.
I can do it if it's aligned with the goals of Automake in general, to 
support a toolchain which is 10 years old and unmaintained and unsupported 
since many years.

> > I'm in the process of assigning my copyright to GNU.
>
> Great.  Could you ping me when the assignment has been completed?

Sure, will do.

> Your patches are lacking GNU-style ChangeLog entries.  If you could add
> them, that would be great, otherwise I will.  Note that for Automake, we
> typically let the commit log entry be the ChangeLog entry without the
> author attribution and indentation, and with an additional newline after
> the first line.  Also, I'd prefer to have a short first line as summary.
>
> Anyway, as I said if you don't add this I can just do it.

I'll add them, I forgot and use them in some of my own projects 
(pygtk/pygobject/flumotion).

Johan