> On Feb 10, 2017, at 9:24 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > What's supposed to happen is that ensurepip installs a fresh copy into > the virtual environment. > > It *doesn't* happen under Python 3 on Fedora when system site-packages > is visible, because if python3 is installed, then python3-pip will > *also* be installed, and you get the behaviour you're seeing. > > So this should be filed as a bug against the Fedora python package for > doing the wrong thing by default. > > However, it isn't clear that this qualifies as an upstream bug, as > ensurepip in general is *supposed* to be a no-op when pip is already > installed. >
It’s not a Fedora bug really, it’s a venv bug, virtualenv has special logic to ensure pip actually gets installed with system site packages and when we Implemented that in venv I forgot to do it. It looks like it’s already been fixed upstream - https://bugs.python.org/issue24875 <https://bugs.python.org/issue24875>. — Donald Stufft
_______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
