byterun
byterun copied to clipboard
Travis-CI integration
Just automatically do the tests on travis-ci
@alanjds Could you do me a favor and squash these commits down to one? Also, I'm curious what you're using byterun for. :)
Also, a thing I learned about tox: the -e parameter is read from a TOXENV environment variable if it exists, so if you set TOXENV instead of TOX_ENV, then you can simply use "tox" instead of "tox -e $TOX_ENV".
Hum... my GIT knowledge seems subpar, as I have no clue on how to squash things.
For tox, I just grabbed some recipe floating around and it worked. I will update with your proposal.
I am investigating several ways to run Python in an Android browser. The Brython implementation is fast, the PyPy.js one is compatible. Brython have no bytecode, PyPy.js does. One line of work is making byterun runs right on Brython, and PyPy.js complile stuff to bytecode before sending the bytecode to the browser, to be ran via byterun->Brython.
Anyway, this seems reasonable?
Here are good instructions on how to squash the commits: http://davidwalsh.name/squash-commits-git
You have an interesting idea, I did not think that byterun would be used to actually run Python code. I wonder what the performance would be like...
Nice. Thanks.
(...) I did not think that byterun would be used to actually run Python code. I wonder what the performance would be like...
??? Well, I guess this is what it has made for, dont ;) ?
The idea is to feed python into CPython/PyPy locally, store the .pyc, spin byterun on Brython in the browser and feed the stored .pyc to byterun.
If performance sucks, reimplement some parts in javascript, as Brython allows it. Worst than non-JIT PyPy.js it will not be...
Uhh...I know PyPy.js takes forever to load, but I'm also sure that the JIT would kick in with something like byterun. Even without the JIT, Brython still is not the fastest kid on the block...
I noticed this too, but with JIT PyPy.js crashes on Android.
@alanjds Are you sure? I have a web app that uses PyPy.js, and I use it from Chrome on Android all the time. Maybe it's actually the wrapper JS? Besides, you should probably file that as a bug...
...or Android Browser crashes, to be correct.