"To try it, you need: a recent version of PyPy: PyPy 1.3 does not contain the necessary logic to work with virtualenv, so you need a more recent PyPy from subversion trunk. You can either build it by yourself or download one of our precompilednightly builds a copy of virtualenv-pypy: this is a fork of virtualenv that contains all the patches needed to work with PyPy, and hopefully will bemerged back at some point."
"The directory layout has been redesigned in a way that it is possible to use virtualenv to install a PyPy both from a precompiled tarball or from an svn checkout: # from a tarball $ virtualenv -p /opt/pypy-c-jit-76426-linux/bin/pypy my-pypy-env # from the svn checkout $ virtualenv -p /path/to/pypy-trunk/pypy/translator/goal/pypy-c my-pypy-env Once the environment has been created, you can enter it as usual. Note that bin/python is now a symlink to bin/pypy. Enjoy it :-)"
Virtualenv supports creating PyPy-based virtual environments when used with a recent PyPy build and a patched virtualenv fork called virtualenv-pypy. PyPy 1.3 lacks the necessary logic, so obtain a newer PyPy from the subversion trunk or use precompiled nightly builds. virtualenv-pypy includes the patches required for PyPy and remains compatible with standard virtualenv usage, including creating non-PyPy environments. The directory layout has been redesigned so virtualenv can install a PyPy from either a precompiled tarball or an svn checkout using the -p option. After creation, bin/python is a symlink to bin/pypy and the environment is entered as usual.
Read at Antocuni
Unable to calculate read time
Collection
[
|
...
]