search

sgzwiz / brython

Automatically exported from code.google.com/p/brython
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

consider merging with another browser python implementation? #70

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
For example, http://www.skulpt.org

Skulpt looks to have much more complete support for Python syntax and language 
features; however, Brython has much more complete access to browser facilities 
such as the DOM.  Skulpt requires lots of ugly boilerplate bootstrap code  
(See, for example, https://github.com/bnmnetp/skulpt/issues/49).

These two projects appear to have compatible licenses; it would be great if 
they could merge into a unified effort.

(My dream, personally, would be to get rid of the Python-in-Javascript parsers, 
and spend this effort instead on a PyPy JavaScript back-end, since PyPy already 
has a great Python compiler in Python.  But, PyPy is a much bigger project and 
I could see that merging with it would be a much more significant effort.)

Original issue reported on code.google.com by Glyph.Lefkowitz on 13 Feb 2013 at 1:27

GoogleCodeExporter commented 9 years ago 
Skulpt is a port of cpython to javascript, it's not a good idea if you want 
good performance.

Original comment by j...@jsantos.eu on 18 Feb 2013 at 8:46

GoogleCodeExporter commented 9 years ago 
No, skulpt is written in javascript, but the code is very different.  We could 
probably borrow some implementation ideas from skulpt (and skulpt from 
brython), but since the code is quite different, merging probably won't happen.

Original comment by billy.earney@gmail.com on 27 Feb 2013 at 11:50

GoogleCodeExporter commented 9 years ago 
I agree , effort of two project should be merged to created a better world!

Original comment by phyo.arkarlwin on 29 Apr 2013 at 4:46