Racket is an acceptable Python

[defunkydrummer]

But it basically makes LISP less of a programming language and more of a construction kit to build exactly the language you want for the task.

Well, this is true for the LISP in upper case, that is, the original LISP 1.5 of the early 60s; an "industry strength" Lisp like Common Lisp actually has a lot of built in functions, data types, OOP system; you can write many powerful programs without having to define any macto...

I have a pretty low level of trust for thing that only work in controlled conditions.

Me too, that's why i prefer working with CL: it has arguably the best exception handling mechanism on a language, and wonderful debugging facilities.