Re: Running virtualenv to set the ENV

On Thu, 25 Apr 2019, Cameron Simpson wrote: Personally, I like to treat the virtualenv as a source for third party modules needed by the project. I explicitly do not like to pollute it with project code - that way revision control can ignore the whole venv tree and it can be blown away/rebuilt f

Re: Running virtualenv to set the ENV

Rich Shepard writes: > Which is the CWD for running virtualenv and spcifying the path to the > project's directoy? I mentioned "virtualenv" together with "setuptools". "virtualenv" gives you a (light weight) isolated Python installation (sharing things with the base Python installation). You typ

Re: Running virtualenv to set the ENV

On Thu, Apr 25, 2019 at 2:38 PM Cameron Simpson wrote: > > On 25Apr2019 12:05, Chris Angelico wrote: > >> venv-requirements.txt > >> Periodically I run "pip freeze >venv-requirements.txt"; this file is > >> revision controlled. That way I can rebuild an equivalent venv > >> somewhere else l

Re: Running virtualenv to set the ENV

On 25Apr2019 12:05, Chris Angelico wrote: venv-requirements.txt Periodically I run "pip freeze >venv-requirements.txt"; this file is revision controlled. That way I can rebuild an equivalent venv somewhere else later. Any particular reason for this name? If not, I would generally recomme

Re: Running virtualenv to set the ENV

On Thu, Apr 25, 2019 at 11:40 AM Cameron Simpson wrote: > > On 24Apr2019 16:50, Rich Shepard wrote: > >>Can be either way. What I do is "python3 -m venv env" in the app > >>directory, which creates a subdirectory called "env". (I also have some > >>bash integration that means that any time it see

Re: Running virtualenv to set the ENV

On 24Apr2019 16:50, Rich Shepard wrote: Can be either way. What I do is "python3 -m venv env" in the app directory, which creates a subdirectory called "env". (I also have some bash integration that means that any time it sees a directory called "env", it auto-activates that venv.) So the venv i

Re: Running virtualenv to set the ENV

On Thu, 25 Apr 2019, Chris Angelico wrote: Can be either way. What I do is "python3 -m venv env" in the app directory, which creates a subdirectory called "env". (I also have some bash integration that means that any time it sees a directory called "env", it auto-activates that venv.) So the ven

Re: Running virtualenv to set the ENV

On Wed, 24 Apr 2019, Dennis Lee Bieber wrote: That... sounds backwards... So far as I understand it (I've only used a virtual when following a book for Flask) you create the virtual environment first, and then set up the application development INSIDE that environment. The project dir

Re: Running virtualenv to set the ENV

On Thu, Apr 25, 2019 at 8:55 AM Dennis Lee Bieber wrote: > > On Wed, 24 Apr 2019 09:17:28 -0700 (PDT), Rich Shepard > declaimed the following: > > >I've installed virtualenv in Slackware-14.2. Now I want to set up the ENV > > in an application's >

Re: Running virtualenv to set the ENV [RESOLVED]

On Wed, 24 Apr 2019, Rich Shepard wrote: Which is the CWD for running virtualenv and spcifying the path to the project's directoy? The project's subdirectory. It's up and running now. Rich -- https://mail.python.org/mailman/listinfo/python-list