On Fri, 2017-02-10 at 15:28 +0100, Nick Coghlan wrote: > > On 8 February 2017 at 13:44, Tadej Janež <tade...@nez.si> wrote: > > > > As I see it, there are two issues when one has the aforementioned > > three > > way combination: > > > > 1) Users will probably use 'pip install foo' inside the activated > > virtual environment and be surprised by not being able to install > > anything. > > Many of them might not know the 'python -m pip install foo' > > variant. > > Right, that's why I consider the fact that doesn't work by default a > bug in Fedora's current approach.
Agreed. And I'm very glad that this has already been fixed upstream, so we just have to wait until this lands in Fedora. > > 2) Users that know the 'python -m pip install' variant may want to > > install a package inside the virtual environment that is already > > available in system site-packages . The installation won't work > > unless > > they pass the '--ignore-installed' option or they install a newer > > version of the same package with '--upgrade' option. > > This, on the other hand, is why having the system site-packages > visible is discouraged in general - it really is more complicated > than > using an environment that only shares that standard library and the > language runtime. Agreed. This is a caveat with using the system site-packages and one has to accept such things if he needs a virtual environment with the system site-packages enabled. Thanks again for clearing this up for me! Regards, Tadej _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
