Okay, I've reread your posts. Would you say this is an accurate summary of your argument:

Python is aesthetic and Python is poor at prototyping, therefore aesthetic is bad for prototyping.

I'd appreciate if you also clarified the following:

• why do you think Python is bad at prototyping?
• which language do you think are good at prototyping, and why?
• do you think these languages are bad at production, and why?
• do you not indent your code?
• what do you deem to be a prototype (days needed, kloc, or some other metric)?

Regarding my comment about prototypes morphing into production, that's only a red herring if a languages that are good at prototyping are necessarily poor at production (I don't agree with that). It's also a valid concern since it is is a common progression with today's software; the whole agile/iterative/refactoring methodologies are a response to this.