This repository contains efforts to build 64 bit x86 PyPy binaries for various Linux distributions. The idea is that you just download an archive, uncompress it and run it instantly without installing any extra libraries or tweaking your OS. Currently they are known to work across various DEB and RPM based distributions including RHEL/Centos 6 and later, Fedora, SuSE Linux, Ubuntu and Debian stable. PyPy binaries should run on any distribution that includes glibc 2.17.
md5: 642aa33f07f93c220eb5188048d6ce6f sha1: 47e889dc0880eaba71b669c41522f8fc8f583393 sha256: 07f16282d126abfa759702baea869b0f661aa97f4c553ebec66c624bda28155f
md5: c78a3b9890f6a06485d350bf460debcd sha1: 9d98ab759abd809e9388d5214e9d3ffaf4f9118e sha256: 1d2a833680f9432b6b5f6b8503f656535f429eeb6c4bc5408abe5b637bfb9b94
All downloads can be found here
For your convenience this build also includes packaged virtualenv so you don't have to install one if you haven't done it yet:
portable-pypy/bin/virtualenv-pypy my-environment
In this case you don't have to add -p switch as it defaults to pypy binary
located in the build.
Stock virtualenv didn't work with portable binaries prior to version 2.3 that included RPATH
entries in pypy binary. For these versions it's obligatory to use
virtualenv-pypy that fixes this problem.
Besides PyPy there is OpenSSL, SQLite3, libffi, expat, TCL/TK and virtualenv packaged in these builds.
This software bundles OpenSSL. Each build has a version of OpenSSL that was most recent and stable at the time of packaging this software. This is done because OpenSSL versions used across distrubtions in last 10 years greately vary and they are not compatible in ABI nor API way. This also means that if there is a major security issue with OpenSSL updating your system OpenSSL will not solve it for Portable PyPy. If you are looking for tight integration with your distribution you should probably wait until your distribution vendor packages version of PyPy you want to use or you can notify me and wait for a new build.
The ssl module will try to locate and use your system certificate store. Namely it will look for a /etc/pki/tls/certs/ca-bundle.crt file (RHEL derived systems) and then look for a /etc/ssl/certs directory (Debian dervied systems). Finally it will fallback to bundled Mozilla trust stores extraced from certifi project. If you don't like this behavior or your system trust store is located somewhere else you can use SSL_CERT_FILE and SSL_CERT_DIR environment variables to point it somewhere else.
Binaries are built with a CentOS 6 base image with help of docker. That ensures that they are built against version of GLIBC that is reasonably old not to cause problems with symbol versioning. All the dependencies are also built inside chroot from latest stable tarballs. They are packed together with PyPy into one distribution and RPATH entries are inserted into them (this ensures that they can be found relatively to each other).
If you want to build it yourself checkout instructions inside BUILD.rst.