Hi Donald, On 12 May 2014 18:39, Donald Stufft <don...@stufft.io> wrote: > I have a half written patch to backport ensurepip to PyPy, I just got confused > trying to test it and task switched to cover some other things. > > As far as virtualenv goes, instead of virtualenv I’d much rather that you > backport > the venv module. It does require some interpreter changes but I don’t think > they are particularly hard.
I am myself not following closely these various packaging schemes, but I do know that with any Python or PyPy installation, I need a working pip and often a virtualenv. So from my own point of view, these two are the most used pieces of software I need from a PyPy installation --- the ones I have to worry about and reinstall every time, and every time I need to google around for how this is done exactly. Anything else can be installed from there. So that's why I'd suggest we include these two exactly. In particular, I don't see "ensurepip" as intrinsically solving anything for PyPy (here talking about the 2.7 version only) --- most people just need "pip". Same about virtualenv --- sorry, it's the standard, and I don't see the point of adding a different one (again, talking about the 2.7 version only. If CPython 3.x decides to include ensurepip or whatever, we can follow suit on PyPy3). A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
