It’s a tough culture to introduce in an IT shop that’s used to more “fire fighting” than designing.

That’s why Nathan Weizenbaum started the Marmalade repository for Elisp packages, which is designed for package.el. So, I’m still kind of wondering: does el-get have an advantage over package.el (included in Emacs), since both can can connect to arbitrary repositories?

Thanks,
Tom Davey

While ELPA is a great thing to have, it’s so easy to find some high quality Emacs extension out there that are not part of the offer. Either authors are not interrested into uploading to ELPA, or they don’t know how to properly package for it (it’s only simple for single file extensions, see).

So el-get is a pragmatic answer here. It’s there because it so happens that I don’t depend only on emacs extensions that are available with Emacs itself, in my distribution site-lisp and in ELPA. I need some more, and I don’t need it to be complex to find it, fetch it, init it and use it.

Of course I could try and package any extension I find I need and submit it to ELPA, but really, to do that nicely I’d need to contact the extension author (upstream) for him to accept my patch, and then consider a fork.

Basically, not everything I want is necessarily in ELPA.

Thanks,
Tom Davey

class A(object):
def __init__(self):
cls = type(self)
while cls != A:
cls = cls.__base__
super(self.__class__, self).__init__()

class B(A):
def __init__(self):
super(B, self).__init__()
inside __init__():

In this example, I walk through all the base classes, until I reached the actual base class A.
Then, instead of providing self.__class__ to super() it would do the same, like when I call super(A.__class__, self).
So it’s possible with python2.6 to use generic constructors.