I'm angling for Lisp, as I'll be working through SICP over the next N months anyway. Even if it turns out that I never develop anything real in it, I think it would be more beneficial to really understand Lisp than it would to be proficient in Python.
I'm a big fan of lisp but I have to say that a solid understanding of Python has been a lot more beneficial to me than Lisp. While I like the mind expanding concepts of Lisp I find that I use Python for almost everything on a daiky basis. Lisp has been fun to learn but I've rarely used it since so if I had to pick I would learn Python before Lisp.
It does look like a good tutorial. In the meantime, you can take a small (ok, trivial) step by not spelling it "LISP" (a pet peeve of many Lisp hackers).
It doesn't matter, because this method is somewhat archaic anyways.
You might want to consider how horizontal share-nothing apps tend to work. You can combine share-nothing with continuation-based web servers if you have a smart and fast dispatcher sitting above your cluster of responders. I'm working on fixing that in Fuzed ( http://github.com/KirinDave/fuzed/tree/master )
You might want to quickly whip up a fuzed binding for CL and give it a try, it makes wiring any language to a webapp as simple as responding to a binary protocol. This might seem like a sidestep to the actual problem, but it actually has a lot of nice side effects in terms of your organization of discrete responders.
Had I been awake, I would not have asked such a silly question. The answer is "Of course there is!" Google is your friend. There is a semi-generic Mod-Lisp package and at least one wrapper for it cl-modlisp... The rest is left as an exercise for the reader.
Now I have no idea what language to try next, either learn Python and Django or try Lisp.
Hmm.