Python, client side: Skulpt
skulpt.org
Python, client side: Skulpt
1–10 of 43 posts
Re: Python, client side: Skulpt
#2I just can't get myself to love JS the way I do other languages... so, this is my current little weekend project.
It's a source-to-source translator so it interops reasonably with JS and should perform similarly also.
The parser is derived from CPython's so that part is relatively complete, but the "backend" isn't done yet. For example, there's not even support for "class" yet.
Re: Python, client side: Skulpt
#3I just can't get myself to love JS the way I do other languages... so, this is my current little weekend project. It's a source-to-source translator so it interops reasonably with JS and should perform similarly also. The parser is derived from CPython's so that part is relatively complete, but the "backend" isn't done yet. For example, there's not even support for "class" yet.
Neat little thing. Feared and appreciated comprehensively.
Re: Python, client side: Skulpt
#4I just can't get myself to love JS the way I do other languages... so, this is my current little weekend project. It's a source-to-source translator so it interops reasonably with JS and should perform similarly also. The parser is derived from CPython's so that part is relatively complete, but the "backend" isn't done yet. For example, there's not even support for "class" yet.
Very impressive work. But you'll need to implement "import this" for it to be considered a serious Python implementation.
Re: Python, client side: Skulpt
#5Fun stuff. I've got a similar proof-of-concept project for Ruby, called "CappRuby" which targets the Objective-J runtime (not unlike how MacRuby targets the Objective-C runtime):
http://github.com/tlrobinson/cappruby
(disclaimer: it's horribly incomplete and I haven't touched it in months)
Re: Python, client side: Skulpt
#6I just can't get myself to love JS the way I do other languages... so, this is my current little weekend project. It's a source-to-source translator so it interops reasonably with JS and should perform similarly also. The parser is derived from CPython's so that part is relatively complete, but the "backend" isn't done yet. For example, there's not even support for "class" yet.
Did you evaluate PyPy? I think they already have a significant RPython->Javascript backend.
Re: Python, client side: Skulpt
#7I just can't get myself to love JS the way I do other languages... so, this is my current little weekend project. It's a source-to-source translator so it interops reasonably with JS and should perform similarly also. The parser is derived from CPython's so that part is relatively complete, but the "backend" isn't done yet. For example, there's not even support for "class" yet.
Did you evaluate PyPy? I think they already have a significant RPython->Javascript backend.
Link? I don't see it at http://codespeak.net/pypy/dist/pypy/doc/docindex.html#pypy-d... (a js interpreter, but no translator).
If I were to guess, not having seen PyPy's: I'd like something about 100x smaller than PyPy seems to be, and I don't want a mandatory up-front translation "build" step.
Re: Python, client side: Skulpt
#8Fun stuff. I've got a similar proof-of-concept project for Ruby, called "CappRuby" which targets the Objective-J runtime (not unlike how MacRuby targets the Objective-C runtime): http://github.com/tlrobinson/cappruby (disclaimer: it's horribly incomplete and I haven't touched it in months)
Neat.
ObjJ and Capp were my inspiration for doing a browser language without an offline convert process, so... thanks :)
I was wondering if I could use Cappuccino as the "Skulpt GUI toolkit" too, but that might start to get a bit silly with number of layers involved.
Re: Python, client side: Skulpt
#9Earlier quoted context omitted.
Did you evaluate PyPy? I think they already have a significant RPython->Javascript backend.
Link? I don't see it at http://codespeak.net/pypy/dist/pypy/doc/docindex.html#pypy-d... (a js interpreter, but no translator). If I were to guess, not having seen PyPy's: I'd like something about 100x smaller than PyPy seems to be, and I don't want a mandatory up-front translation "build" step.
Apparently they removed it:
http://www.mail-archive.com/pypy-dev@codespeak.net/msg03946....
That post also mentions Pyjamas, a port of Google Web Toolkit which compiles Python instead of Java: http://pyjs.org/
Re: Python, client side: Skulpt
#10I just can't get myself to love JS the way I do other languages... so, this is my current little weekend project. It's a source-to-source translator so it interops reasonably with JS and should perform similarly also. The parser is derived from CPython's so that part is relatively complete, but the "backend" isn't done yet. For example, there's not even support for "class" yet.
What version of the language is this and what subset of stuff works, it seems like everything I try gives me some kind of error, maybe I'm just picking the wrong things.
like it lets me create a dictionary but if I try to call the iterkeys() method it doesn't like that, and the built-in function dir() doesn't work. It has range() but not xrange()?
Cool none the less.