There are so many things you should be doing to determine the cause of "it ain't working" it's almost unreal. But before answering in more detail, it's important that you know what pyjamas is and is not. First off: pyjamas is a compiler, not a debugger. It's the equivalent of "gcc". Actually, if you know how gcc works, pyjsbuild is the equivalent of "gcc" and pyjscompile is the equivalent of, for example, "/usr/lib/gcc/x86_64-linux-gnu/4.3.3/cc1". In other words, gcc and pyjsbuild are the general-purpose "front-ends", and cc1 and pyjscompile are the actual nitty-gritty compilers.

You need to be aware of this because you cannot expect pyjamas, a specialist compiler, to also take on the task of being the debugger, or to incorporate the tasks performed by tools such as pylint, or to be the virtual machine under which the javascript executes, or to be a javascript code-compressor, or to do any other task other than actual compiling.

With that in mind, here are some things that you can do:

Overall, then, it's important to remember that pyjamas is a compiler, not an interpreter, not a debugger, syntax checker or anything else other than a compiler. This may be a bit of a shock if you are used to the python interpreter throwing helpful stack traces for you - which is what Pyjamas Desktop is there for: it actually runs Pyjamas applications as real python, not as javascript.