Yeah, virtual environments tend not to have python/pip with a version suffix. So important to use just python/pip once the virtual environment activated else can fallback to system Python.
I would strongly recommend not creating the virtual environment as root. Use a normal user and then also install all Python packages into the virtual environment as the non root user. Only use the root user when installing the system packages, not the subsequent virtual environment creation and Python package installation. Graham > On 24 May 2018, at 6:51 am, Tim Buckland <[email protected]> wrote: > > Thanks very much Graham, > > I followed the links in your doco and eventually cottoned on that I'd created > a Python 2 virtual environment and fooled myself into believing it was > accepting my pip3 commands, but obviously it was just ignoring me and > installing to the main environment. > > Then once you have setup the virtual environment correctly and activated it > you can switch to using python and pip instead of python3 and pip3. > > It seems to be working smoothly now! > > Regards, > > Tim > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/modwsgi > <https://groups.google.com/group/modwsgi>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
