Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #57918 > unrolled thread

Re: How do I update a virtualenv?

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.

Contents

  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

#57918 — Re: How do I update a virtualenv?

> Where specifically are these instructions that tell you to put the
> virtualenv under VCS control?

https://devcenter.heroku.com/articles/getting-started-with-python

> As you are a Heroku customer (I'm not), would you be willing to
> suggest they alter them based on advice from this forum?

It's not my job to pretend to be an expert about something I am
clearly not. All I would be doing is passing along your perspective on
the matter. I presume they have reasonable reasons for doing things
the way they do it. It would be better for people expert in VCS issues
to discuss this stuff with the Heroku people, who presumably know a
thing or two about application deployment, and can give you their
perspective on why they use "git push" as a deployment tool.

Skip

[toc] | [next] | [standalone]

#57991

On 30/10/2013 12:08 AM, Skip Montanaro wrote:
>> Where specifically are these instructions that tell you to put the
>> virtualenv under VCS control?
>
> https://devcenter.heroku.com/articles/getting-started-with-python

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.

[toc] | [prev] | [next] | [standalone]

#58046

> 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

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web