Even the clojure contrib jar is not included by default and has to be downloaded separately and then clojure needs to be launched with extra command line arguments to setup the classpath properly (or you need to fiddle with the classpath from within clojure), the same goes for any Java library that you want to use.
Even by itself, that is better than most Lisps out there, if not enough to make a Pythonista happy. The problem with this stuff is usually the painful verbosity of Java necessary to use it, but you can wrap away that pain very quickly with Clojure.
I do take the point about needing to fiddle with the classpath for any other Java code you want to use. But for me the Java classpath system holds up better than most other software deployment mechanisms. Usually, you just download a jar file, drop it on your classpath, and it just works. I think jar files are an unappreciated success story of the Java ecosystem. Clojure has functions to easily add jars to the classpath at runtime, which is even better, but I find it does not always work seamlessly for me.
In many ways, Clojure seems like a deliberate response to each of the common complaints against Lisp.
Hard to call Clojure "old" when it's only been around a couple years. Clojure has been very successful at building nerd "street cred." It has latched onto the fascination with functional programming for parallel applications, for one. It also makes use of concise syntax for data structure literals, like Python and Ruby, too. Dynamic, etc. etc. Don't think Clojure has this problem. Clojure gets the performance benefits of running on the highly tuned JVM, with tricks like type hints to get close to Java speeds for critical portions of code. Worst case, you can always drop into Java as your "assembly" language. Clojure mixes up () with [] {} to make code easier to mentally parse. No change here. Clojure is pretty small and doesn't take much time to get started. Some might start to think "Clojure is all about functional programming." Don't know if that's good or bad. There's only one Clojure implementation. You get all the libraries written for Java. I use Emacs, which is also great for Clojure, so I can't judge how easy it is to program in Clojure without Emacs. You might be able to sneak Clojure into a Java shop.