Hi Armin,
The way to think about cloud application platforms like Heroku, Bluemix,
and Cloud Foundry is that they provide you with a working Linux box and little
else. Therefore you use a "buildpack" (like an install script) to bundle up
all your executable environment, libraries, and code so that it can be loaded
and run on a remote Linux box.
In the case of CPython that means that the buildpack needs to install a
working CPython, setuptools, and pip, etc. and then look in your
requirements.txt to find which pypi modules pip needs to install and then it
launches your webapp (written to django, flask, bottle, etc.).
To get Pypy to work in place of CPython, the buildpack would need to
install a working Pypy, setuptools, and pip. Libffi is an essential precursor
to having Pypy work properly. Some interesting work was done in
https://github.com/mfenniak/heroku-buildpack-python-libffi/blob/master/bin/steps/libffi
to get libffi working in a buildpack but my limited understanding does not
allow me to take that further.
It would be of interest to get Pypy working on these Platform-as-a-Service
environments in place of CPython but it is beyond my limited understanding to
actually make it happen.
I hope to see your presentation at EuroPython.
On 16 Jul 2014, at 14:50, Armin Rigo <ar...@tunes.org> wrote:
> Hi Chris,
>
> On 16 July 2014 14:29, cclauss <ccla...@me.com> wrote:
>> The plan is to support Pypy on Heroku, but we need to have full libffi
>> support before we move forward.
>
> What does this mean, exactly? You don't provide libffi on your build
> system, and so PyPy cannot be built there?
>
>
> A bientôt,
>
> Armin.
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
