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 using pipenv/pip is to make the venv easy to recreate. That being said I would focus more on whether my pipfile/requirements.txt is maintained properly or not. If it is then spinning up the same venv is an easy task. On Wed, Mar 27, 2019, 4:21 AM Tim Johnson <t...@akwebsoft.com> wrote: > * Test Bot <onlinejudg...@gmail.com> [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, but I am assuming that in the book, every > > chapter builds on the previous one). > The author's source code is on github, so I downloaded all of it > for my edification. > > It appears that consecutive chapters do not always build on the > following, i.e. have the previous chapter files. > > I guess I will find out why ... > thank you > > On a personal note it sounds strange why the author wants to have > different > > venv's for each chapter. > > > > On Wed, Mar 27, 2019, 3:30 AM Tim Johnson <t...@akwebsoft.com> wrote: > > > > > 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 > > > helloworld-_e28Oloi > > > pages-Du4qJjUr > > > > > > What would happen if I deleted the first folder, which was created > > > in a previous chapter? > > > > > > ... trying to minimize my SSD real estate. > > > thanks > > > -- > > > Tim Johnson > > > http://www.tj49.com > > > -- > > > https://mail.python.org/mailman/listinfo/python-list > > > > > -- > > https://mail.python.org/mailman/listinfo/python-list > > -- > Tim Johnson > http://www.tj49.com > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list