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
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
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
I have a virtualenv I'm using for some Django development. Today I
switched from MacPorts to HomeBrew on my Mac. I'm thus getting a
different version of gcc and its libs. How do I reinstall the
virtualenv? I've looked around and found a few descriptions of what to
do, but as I am little more than
On 10/28/13 7:04 PM, Skip Montanaro wrote:
I have a virtualenv I'm using for some Django development. Today I
switched from MacPorts to HomeBrew on my Mac. I'm thus getting a
different version of gcc and its libs. How do I reinstall the
virtualenv? I've looked around and found a few
In article
canc-5uy367mu-zn30z8xkfe_zf9q4g15e_ovtb+howpja6m...@mail.gmail.com,
Skip Montanaro s...@pobox.com wrote:
I have a virtualenv I'm using for some Django development. Today I
switched from MacPorts to HomeBrew on my Mac.
Any particular reason for doing that? That seems like a step
Virtualenvs aren't built to be moved from one Python installation to
another. If you used pip to install your packages (you should), then you
can activate the virtualenv, and run: $ pip freeze requirements.txt
Then you can create a new virtualenv using the new Python executable,
activate
On 10/28/13 7:53 PM, Skip Montanaro wrote:
Virtualenvs aren't built to be moved from one Python installation to
another. If you used pip to install your packages (you should), then you
can activate the virtualenv, and run: $ pip freeze requirements.txt
Then you can create a new virtualenv
I have a virtualenv I'm using for some Django development. Today I
switched from MacPorts to HomeBrew on my Mac.
Any particular reason for doing that? That seems like a step backwards,
especially for Python-related work.
The guy who sits next to me at work recommended HomeBrew. (Someone to
Skip Montanaro s...@pobox.com writes:
Hmmm... And my git repo?
You are keeping your virtualenv separate from your working tree, right?
I put mine in ‘/var/local/devel/$USER/virtualenvs/foobar/’ where
“foobar” is the specific virtualenv name.
This allows an arbitrary number of virtualenvs
In article mailman.1731.1383006012.18130.python-l...@python.org,
Ned Batchelder n...@nedbatchelder.com wrote:
pip install --upgrade will upgrade your Python packages. pip install
-r requirements.txt will install new packages or versions named in the
requirements.txt file.
Yup, that's
Hmmm... And my git repo?
Usually the virtualenv is outside the git repo (and vice-versa), but git
repos are also easy to recreate from the git server if you need to. Maybe I
don't understand what you mean?
I'm using Heroku, following their instructions. They have a git init
in the midst of
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
Hmmm... And my git repo?
You are keeping your virtualenv separate from your working tree, right?
I put mine in ‘/var/local/devel/$USER/virtualenvs/foobar/’ where
“foobar” is the specific virtualenv name.
No, I'm no expert in these things. I was just following the directions
on the Heroku
Skip Montanaro s...@pobox.com writes:
I'm using Heroku, following their instructions. They have a git init
in the midst of things, so I wind up with a git repo that matches up
one-to-one for my Django project. (git push installs).
That's not a good thing; you don't want loads of third-party
Skip Montanaro s...@pobox.com writes:
You are keeping your virtualenv separate from your working tree,
right? I put mine in ‘/var/local/devel/$USER/virtualenvs/foobar/’
where “foobar” is the specific virtualenv name.
No, I'm no expert in these things. I was just following the directions
16 matches
Mail list logo
