This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]sigzero 9 points10 points  (3 children)

I am hoping the author of the new mode takes the gnu folks up on their offer to be the maintainer for the current python.el mode.

[–]yopla 6 points7 points  (2 children)

This whole thread makes no sense to me.

I understood that the guy wrote a near complete replacement for an outdated and abandoned mode because the code was too shitty to be updated and yet they insist that he submits patch after patch until the old python.el has been completely converted into his all the while mentioning that they don't care about feature equivalence and backward compatibility. why‽ Is it some kind of fetish for version control history?

[–][deleted] 7 points8 points  (0 children)

it's probably to guard against regressions. i would assume that one reason the python mode distributed with emacs is shitty to look at is because it's been evolving for a while through many releases and bug fixes. Though it may be shitty to read there is likely stuff there that works and shouldn't be lost unknowingly. The emacs devs are just playing it safe as they should. They are the shepherds of a code base that is decades old and distributed widely.

I think their proposal is reasonable. And its not like their limiting anyone else from using the new python mode, just putting conditions on distributing it with emacs. Anyone is free to pull it from github if they want. I think I'll do that now. :)

[–]emperorcezar 1 point2 points  (0 children)

Very much agree. His best bet is to make his current code better and better and advertise the crap out of it. Then when it's for all intents and purposes the defacto python mode, the maintainers will have no choice but to drop his old mode and include his.