Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #58046
| References | (3 earlier) <526EFDAF.9010109@nedbatchelder.com> <CANc-5UxvqRuEoW3PEVxDnA+64SGTPQ9qWWnTOB0L8oMd2+G_LQ@mail.gmail.com> <7wmwlszsmr.fsf@benfinney.id.au> <mailman.1760.1383055740.18130.python-list@python.org> <l4po8v$evn$2@dont-email.me> |
|---|---|
| Date | 2013-10-30 10:18 -0500 |
| Subject | Re: How do I update a virtualenv? |
| From | Skip Montanaro <skip@pobox.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1811.1383146329.18130.python-list@python.org> (permalink) |
> I believe you may have misread the instructions slightly. You should have a > project structure like this: > > my_project/ > /venv > .gitignore > > The instructions mention adding 'venv' to your .gitignore, so it will be > excluded from version control. If you have .git & .gitignore files inside > your venv folder, then you've changed directory into it when you should be > calling it from the project root instead. I have .git and .gitignore at the top level, and venv is in .gitignore. I did, indeed, misunderstand things though. That's the problem with monkey-see-monkey-do. I completely glossed over the part where venv was excluded from my git repo. That being the case then, to update my virtualenv, I need to first create a new one in a fresh directory (using my existing requirements.txt file). I should be able to simply swap out the old venv directory for the new one. Skip
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: How do I update a virtualenv? Skip Montanaro <skip@pobox.com> - 2013-10-29 09:08 -0500
Re: How do I update a virtualenv? alex23 <wuwei23@gmail.com> - 2013-10-30 11:44 +1000
Re: How do I update a virtualenv? Skip Montanaro <skip@pobox.com> - 2013-10-30 10:18 -0500
csiph-web