Re: Retroactively seting up virtualenv

2017-07-16 Thread Antonis Christofides
Hi, once you understand what virtualenv does, it should be obvious. And virtualenv is really quite simple. This should help: https://djangodeployment.com/2016/11/01/virtualenv-demystified/ Regards, Antonis Antonis Christofides http://djangodeployment.com On 2017-07-14 18:30, Rich Shepard wrote

Re: Retroactively seting up virtualenv

2017-07-14 Thread Alceu Rodrigues de Freitas Junior
I guess you don't need to do anything besides running "source /bin/activate" to use your new virtualenv ("whatever" should be directory where it is located). Em 14/07/2017 12:30, Rich Shepard escreveu: My business is not web site development and I'm starting development of a django project

Retroactively seting up virtualenv

2017-07-14 Thread Rich Shepard
My business is not web site development and I'm starting development of a django project for my own use. Django-1.11.3 is installed in /usr/lib/python3.6/site-packages/django and my project is located in / ~/development/clientmgntsystem_project/. I had no issues the last time I ran 'python ma