[Checkins] SVN: zc.buildout/branches/documentation/doc/system-python-virtualenv-and-buildout.rest Cleaned up whitespace.

[Jim Fulton]

Log message for revision 122998:
  Cleaned up whitespace.
  

Changed:
  U   zc.buildout/branches/documentation/doc/system-python-virtualenv-and-buildout.rest

-=-
Modified: zc.buildout/branches/documentation/doc/system-python-virtualenv-and-buildout.rest
===================================================================
--- zc.buildout/branches/documentation/doc/system-python-virtualenv-and-buildout.rest	2011-09-29 10:11:25 UTC (rev 122997)
+++ zc.buildout/branches/documentation/doc/system-python-virtualenv-and-buildout.rest	2011-09-29 11:53:40 UTC (rev 122998)
@@ -18,14 +18,14 @@
 Here are some reasons for isolate egg installation:
 
   * You may not have write access to the main Python environment
-  
+
   * You want to experiment with a egg but not pollute your main Python
     environment
 
   * There is no easy way to differentiate eggs which have been installed in
     the Python environment by yourself or by system-level package installers
     (Ã  la Red Hat).
-  
+
   * While developing in Python you may depend on a system-level Python
     package. Someone consuming your software may not have the required system
     library or worse may have an incompatible version of this required
@@ -35,7 +35,7 @@
 Package/egg isolation are design goals of both virtualenv and Buildout.
 Buildout's design allows for isolation but, unlike virtualenv isolation, is
 not buildout's primary goal. Let's install both environments and look at how
-they work. 
+they work.
 
 You will need curl and version 2.4 of Python or later. Do not install Python
 3.0 or higher at this point. You should download binary versions:
@@ -43,7 +43,7 @@
   * curl with SSL can be downloaded from http://curl.haxx.se/download.html
 
   * Python can be downloaded from http://python.org/download/
-  
+
 Let's create a sandbox with virtualenv and install 2 eggs, nose and mock.
 
 On Linux::
@@ -87,13 +87,13 @@
 mybuildout/bin/buildout. The above bootstrap.py usage is a shortcut to
 generate a config file (buildout.cfg) which bin/buildout uses to assembly the
 environment. The normal process is edit .cfg file and re-run buildout which
-re-generates the sandbox.  
+re-generates the sandbox.
 
 If you look at the buildout.cfg you will see::
 
   [buildout]
   parts = py
-  
+
   [py]
   recipe = zc.recipe.egg
   eggs = nose
@@ -125,7 +125,7 @@
 mybuildout/bin/nosetests). At any point you can regenerate your sandbox with
 the .cfg file. mybuildout/bin/python script puts eggs into sys.path
 explicitly; edit the mybuildout/bin/python (on Linux) or
-mybuildout/bin/python-script.py (on Windows).  
+mybuildout/bin/python-script.py (on Windows).
 
 In conclusion if you want to isolate your Python environment you can use
 either virtualenv or Buildout. If you work with a mix of C (development