[PyPy-issue] [issue604] pypy and virtualenv with distribute on Mac OS X
pypy-dev-issue at codespeak.net
Thu Feb 17 10:52:44 CET 2011
Antonio Cuni <anto.cuni at gmail.com> added the comment:
ok, let's try to clarify things.
1) I'm trying to go for the least-effort route; there are tons of things that
could be done better, but require time which I prefer to spend on IMHO more
2) maintaining an easy-installable version of virtualenv_pypy costs some time.
If there is anyone willing to do it, fine, but I don't want to be that one :-)
3) anyway, I don't think that releasing our own virtualenv_p is less confusing
than the current situation; then people would have to remind to type
virtualenv_p -p pypy instead of /path/to/virtualenv-pypy/virtualenv.py -p pypy.
It might be more convenient, not less confusing
4) for tests: you need a pypy binary for running virtualenv tests. The easiest
way is to have virtualenv inside the pypy tree; the alternative would be to
setup a new buildslave, which either compiles its own pypy-c or download it from
somewhere, etc. etc.
PyPy development tracker <pypy-dev-issue at codespeak.net>
More information about the Pypy-issue