Key difference between Pyvascript and the other compilers I've seen is a facility for macros performing arbitrary AST manipulations. E.g. in the Pylons environment, you can use _uriOf(Controller.someAction) to have it generate a url in your JS code at compile-time.
Always nice to see competition among compilers, though.
That being said, I think to make this project really work you're going to be responsible for documenting the dom, and providing support for libraries like jQuery.
Thanks for the confusion -- I've made the first paragraphs more clear about PJ's scope.
Title changed: s/compiler/syntax cross-compiler/
EDIT: title changed again
I would call what you have done a source-to-source compiler: it translates from one target high-level language to another. http://en.wikipedia.org/wiki/Source-to-source_compiler
ie. 2 * * 1024? print object.__mro__? slice objects? __call__? etc.
If there's no collateral damage and the JS is clear (e.g. 28 --> Math.pow(2, 8)): do it.
If there's no proper way to express the JS in Python (e.g. instanceof and typeof keywords): do it
If it's really important (only "print" and "self"): do it
These few special cases that mess with your code are all mentioned in a section on the the main page.
And you can easily remove them from the transformations if you want.
I abandoned it when CoffeeScript appeared, but you might find something interesting there.
((typeof print !== "undefined" && print !== null) || console.log)(...)
I may still write a limited one for use in creating code blocks in my project MongoAlchemy (http://mongoalchemy.org/).
That being said, it looks fantastic. :)
You can embed this in a web app and write your client-side code in python-syntax. Would work specially well if you server-side code is also in python.