''Morn, welcome to CLiki! Would you mind telling us a little about your connection with Lisp? --(David Owen)''
Well, from time to time I like to toy with the various Common Lisp implementations, but somehow when it comes to using it professionally, so far I've always chosen Python. I suppose when you have code to share with other people (and especially other scientists, who may only be able to program in Fortran or IDL), you have to compromise a little. :-)
What got me interested in Common Lisp (almost ten years ago I think) were (a) the 1970s Lisp culture as vividly portrayed in the Jargon File and (b) Paul Graham's books, i.e. "On Lisp" and whatever the first one was called, I think simply "ANSI Common Lisp". Yes, I think CL's way of doing OO with CLOS is more powerful than Python's, although Python OO is relatively tolerable. But let's say I totally agree with what Lispers like Graham say, that e.g. OO in C++/Java is clumsy by comparison.
Like I said, right now I mostly use Python, but I wonder if Python 3 will change that. It might turn out to be the equivalent of Perl 6, i.e. a moment where many users jump ship. That Star Trek game is a good example: The CL ports work flawlessly for me, while Eric Raymond's Python port crashes all the time. Python 3 might be a good opportunity for me to reconsider CL and see if the library situation has improved to the point where it can compete with Python. I'll do some more reading on CLiki and elsewhere to find out...