summaryrefslogtreecommitdiff
path: root/HACKING.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2013-03-13 15:13:37 -0700
committerChris McDonough <chrism@plope.com>2013-03-13 15:13:37 -0700
commit13e241b21770a2471d520aa21b27e20f98aaecb3 (patch)
tree913c9bf716432b8a1cd8e0e5779196c757eea117 /HACKING.txt
parent6d62d124ee8ffd09459690e34aae95b43d0f2d53 (diff)
parent919643eec1a480cee442331a966a9c6c90fb0965 (diff)
downloadpyramid-13e241b21770a2471d520aa21b27e20f98aaecb3.tar.gz
pyramid-13e241b21770a2471d520aa21b27e20f98aaecb3.tar.bz2
pyramid-13e241b21770a2471d520aa21b27e20f98aaecb3.zip
Merge pull request #910 from tshepang/venv
consistency: use $VENV whenever virtualenv binaries are used
Diffstat (limited to 'HACKING.txt')
-rw-r--r--HACKING.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/HACKING.txt b/HACKING.txt
index 32381cc6c..26e85ee80 100644
--- a/HACKING.txt
+++ b/HACKING.txt
@@ -27,7 +27,7 @@ checkout.
- Install ``setuptools-git`` into the virtualenv (for good measure, as we're
using git to do version control)::
- $ env/bin/easy_install setuptools-git
+ $ $VENV/bin/easy_install setuptools-git
- Install Pyramid from the checkout into the virtualenv using ``setup.py
dev``. ``setup.py dev`` is an alias for "setup.py develop" which also
@@ -36,19 +36,19 @@ checkout.
``pyramid`` checkout directory::
$ cd pyramid
- $ ../env/bin/python setup.py dev
+ $ $VENV/bin/python setup.py dev
- At that point, you should be able to create new Pyramid projects by using
``pcreate``::
$ cd ../env
- $ bin/pcreate -s starter starter
+ $ $VENV/bin/pcreate -s starter starter
- And install those projects (also using ``setup.py develop``) into the
virtualenv::
$ cd starter
- $ ../bin/python setup.py develop
+ $ $VENV/bin/python setup.py develop
Adding Features
---------------
@@ -129,7 +129,7 @@ or adds the feature.
To build and review docs (where ``$yourvenv`` refers to the virtualenv you're
using to develop Pyramid):
-1. Run ``$yourvenv/bin/python setup.py dev docs``. This will cause Sphinx
+1. Run ``$VENV/bin/python setup.py dev docs``. This will cause Sphinx
and all development requirements to be installed in your virtualenv.
2. Update all git submodules from the top-level of your Pyramid checkout, like
@@ -139,7 +139,7 @@ using to develop Pyramid):
HTML docs are generated.
3. cd to the ``docs`` directory within your Pyramid checkout and execute
- ``make clean html SPHINXBUILD=$yourvenv/bin/sphinx-build``. The
+ ``make clean html SPHINXBUILD=$VENV/bin/sphinx-build``. The
``SPHINXBUILD=...`` hair is there in order to tell it to use the
virtualenv Python, which will have both Sphinx and Pyramid (for API
documentation generation) installed.