Re: python.el

[Dave Love]

Glenn Morris <address@hidden> writes:

> Dave Love wrote:
>
>> I explained it to rms, but he wouldn't do anything bug reports
                                                     ^about
>> without patches.
>
> I can't parse this.

Sorry for the typo.

> It was installed by Stefan. I can't speak for him, but I imagine since
> he's the person who installed your python.el initially, and subsequent
> fixes from you,

I don't know what those fixes would be.  It hasn't been helpful
commenting on things when people have complained, unfortunately.

> that he got the impression that there was no problem
> installing updates from your version (which I guess is on the web
> somewhere?).

Yes, since it it's generally useful and recent changes apparently
weren't going to get into Emacs.

> I'm sorry if people complain to you about bugs that aren't your fault.
> There is nothing in the python.el in CVS Emacs that says bug reports
> should be sent to you. It lists maintainer as "FSF".

Sure.  It's more an issue that the bugs are there.

> If something in Emacs does not work, bug reports about it are
> welcome.

I'm afraid they don't seem to be, and I've just given up.

> If changes in some part of Emacs break another, that's bad, but it
> can't be fixed if no-one mentions it.

Of course.  I did a lot of the maintenance for Emacs 21.

> Anyway, back to the topic at hand: there's a potential legal problem
> with python.el. Is all the code you wrote for python.el affected, or
> just the 2006-08-20 changes? Before that, there are no changes from
> python.el from you until we get to 2004-12-02.

Only more recent stuff, I reckon, but I'm not sure exactly what
off-hand.  Anything I didn't send (including to gnu-Emacs-sources) or
install myself is best treated as suspect.

> If it's just the 2006-08-20 stuff: Stefan, is there anyway this can
> easily be removed and still leave a working python.el? Dave, would
> that be acceptable to you?

I guess that's OK.  It's not me I'm worried about, as legal issues
can't damage me.

> Otherwise, our only recourse AFAICS is to remove python.el before the
> (imminent) release of Emacs 22.

Like two or three years ago? :-(.