* Test Bot [190326 15:44]:
> If the chapters are not contiguous then I can't find a reason to delete
> them (previous venv). Moreover it would be better practice to keep separate
> venv and not to use a single venv for multiple codebase. Highly discouraged
> should be to use the systemwide interpr
If the chapters are not contiguous then I can't find a reason to delete
them (previous venv). Moreover it would be better practice to keep separate
venv and not to use a single venv for multiple codebase. Highly discouraged
should be to use the systemwide interpreter.
Moreover the whole idea of us
* Test Bot [190326 14:18]:
> Nothing much i think. If you are properly managing dependencies for each
> venv, then each new venv should have the same state as the previous one
Good to hear
> along with some extra dependencies for each new chapter (haven't gone
> through the specific book, b
Nothing much i think. If you are properly managing dependencies for each
venv, then each new venv should have the same state as the previous one
along with some extra dependencies for each new chapter (haven't gone
through the specific book, but I am assuming that in the book, every
chapter builds
I'm on ubuntu 16.04
using pipenv for the "Django for Beginners..." tutorial book.
each chapter instructs me to create a new virtual environment with a
folder under ~/.local/share/virtualenvs
folders are named with the project name followed by an hyphen and a
brief codified string.
examples
hell
