We are python
30 views
Skip to first unread message
Christian Iversen
Aug 2, 2013, 10:43:22 AM8/2/13
to pyj...@googlegroups.com
Hello World
I want to clarify our mission goals.
I've been thinking a lot about how Pyjaco 1 suffered from being _too_
closely integrated with javascript. It sometimes chose (hackish)
performance improvements over correctness, confusing the user as to
which features were supported and which were not.
No more!
First of all, the new architecture allows for a much cleaner design, but
it also allows for a much truer implementation of *python*. Not
"something that quacks like a duck".
Think about it this way: CPython is the canonical reference
implementation of Python. But there is also PyPy, implemented in Python
itself. And Jython, compiling Python into java bytecode. And IronPython,
running Python on .Net CLR.
Soon, we will have Pyjaco: Running Python on JS. And it wont be "almost"
python, it will _be_ python. We are not far from it already.
And to that end, I've implemented a small wrapper-script (still has bugs
and quirks) that makes an interactive command-line in the style of the
python CLI:
$ ./pyjaco.py
Python 2.7 (pyjaco)
[google v8] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> def foo(x):
... return x+2
>>> foo(4)
6
>>> def bar(x):
... print x.keys()
>>> bar(dict(foo = "bar"))
['foo']
This is also a great way to quickly test ideas and hypotheses about the
compiler. It's _very_ rough and rudimentary as it is now, but it should
be reasonably easy to make it more smooth. There are no real challenges
in that, just a bit of elbow grease :-)
--
Med venlig hilsen
Christian Iversen
I want to clarify our mission goals.
I've been thinking a lot about how Pyjaco 1 suffered from being _too_
closely integrated with javascript. It sometimes chose (hackish)
performance improvements over correctness, confusing the user as to
which features were supported and which were not.
No more!
First of all, the new architecture allows for a much cleaner design, but
it also allows for a much truer implementation of *python*. Not
"something that quacks like a duck".
Think about it this way: CPython is the canonical reference
implementation of Python. But there is also PyPy, implemented in Python
itself. And Jython, compiling Python into java bytecode. And IronPython,
running Python on .Net CLR.
Soon, we will have Pyjaco: Running Python on JS. And it wont be "almost"
python, it will _be_ python. We are not far from it already.
And to that end, I've implemented a small wrapper-script (still has bugs
and quirks) that makes an interactive command-line in the style of the
python CLI:
$ ./pyjaco.py
Python 2.7 (pyjaco)
[google v8] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> def foo(x):
... return x+2
>>> foo(4)
6
>>> def bar(x):
... print x.keys()
>>> bar(dict(foo = "bar"))
['foo']
This is also a great way to quickly test ideas and hypotheses about the
compiler. It's _very_ rough and rudimentary as it is now, but it should
be reasonably easy to make it more smooth. There are no real challenges
in that, just a bit of elbow grease :-)
--
Med venlig hilsen
Christian Iversen
Samuel Ytterbrink
Aug 2, 2013, 6:40:59 PM8/2/13
to pyj...@googlegroups.com
Just a thought can you make it use node. Since node is so much easier to istall then all the other js backends.
--
//Samuel Ytterbrink
--
--
You are subscribed to the Google Group pyj...@googlegroups.com
To unsubscribe from this group, send email to
pyjaco+un...@googlegroups.com
--- You received this message because you are subscribed to the Google Groups "pyjaco - The Python to Javascript compiler" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyjaco+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
//Samuel Ytterbrink
Reply all
Reply to author
Forward
0 new messages