Re: A new major-mode for Python

[Stefan Monnier]

> The possibility of being the maintainer is never a crappy offer, but
> I'm really scared about the effort we would put into doing the kind of
> merge you propose, I can't really see that approach as
> productive. (The mode I wrote shares *very little* code with trunk's
> python.el)

> However since this mode implements the most important features from
> python.el I think we can provide some define-obsolete-function-alias,
> define-obsolete-variable-alias in order to keep it the most compatible
> as possible.

I'm not so much concerned about backward compatibility, really.  I just
would rather have a smoother transition.

> I'm willing to add/re-implement ffap, python-check, skeletons. But I
> can't think of a good reason to add Bicycle Repairman again.

As a maintainer you are free to decide that some feature should
be dropped.  So I don't mind if the repairman goes.  As for skeletons
and ffap, I can't think of any reason why it would be much more work
than just copying the current code: it is pretty self-contained.

> When that stuff is done the new python.el would contain all the
> features of the previous one while adding an important one.

I'm not too concerned about features.  I just want the transition to be
done in meaningful chunks.  E.g. one commit can rip out the old
indentation and install your new one.  Another one could be "drop
bycicle because noone wants to repair the repairman".

> What do you think? It still sounds like a bad idea?

I think we can work something out.  And if Christoph is OK with helping
along, this could go very smoothly.


        Stefan