Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #57869 > unrolled thread
| Started by | Tim Chase <python.list@tim.thechases.com> |
|---|---|
| First post | 2013-10-28 20:46 -0500 |
| Last post | 2013-10-28 20:46 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How do I update a virtualenv? Tim Chase <python.list@tim.thechases.com> - 2013-10-28 20:46 -0500
| From | Tim Chase <python.list@tim.thechases.com> |
|---|---|
| Date | 2013-10-28 20:46 -0500 |
| Subject | Re: How do I update a virtualenv? |
| Message-ID | <mailman.1736.1383011115.18130.python-list@python.org> |
On 2013-10-29 11:42, Ben Finney wrote:
> You are keeping your virtualenv separate from your working tree,
> right?
This was one of the key bits I missed in most of the
virtualenv{,wrapper} documentation and only figured out after asking
several questions here on c.l.p Once I had that understanding, the
usefulness of virtualenvwrapper made more sense (previously, I'd
figured it was silly since I thought the code-base was supposed to be
contained in the virtualenv, not independent from it).
Now it's virtualenv{,wrapper} for just about all development.
-tkc
Back to top | Article view | comp.lang.python
csiph-web