The goal of Brython is to replace javascript on the web, seems straightforward right? The way they go about it is to implement a compiler in javascript, and use that to bootstrap a python in the browser community. Seems like that is much easier than convincing Chrome/Firefox/IE to include a python compiler in their browser.
How would Brython replace javascript if it were precompiled on the server?
One isn't necessarily better than the other - sometimes human generated python source code in the browser may be more useful than machine generated javascript.
If nothing else, it allows us to explore a new way of constructing web apps and determine whether it is better.
I guess it can be solved by gziping the file, or base64 encoding it. But this is also an argument (albeit trivial or weak) for compiling it on the server rather than the client.
CoffeeScript page: "CoffeeScript is a little language that compiles into JavaScript."
Brython page: "Brython is designed to replace Javascript as the scripting language for the Web."
Maybe that's the end goal, but the reality is far from it. Of course JS is still required, and of course the Python gets compiled into JS.
Finally, the approach seems a bit off. I would think it would be better for the Python to be compiled with a pre-processor, not done on the client.