Make zc.buildout a bit more compatible with PyPy.

git-svn-id: http://svn.zope.org/repos/main/zc.buildout/trunk@118848 62d5b8a3-27da-0310-9561-8e5933582275

CHANGES.txt

@@ -4,6 +4,13 @@ Change History
 1.5.3 (unreleased)
 ==================
 
+- changed broken dash S check to pass the configuration options
+  -S -c separately, to make zc.buildout more compatible with the PyPy
+  interpreter, which has less flexible argument parsing than CPython.
+
+  Note that PyPy post 1.4.0 is needed to make buildout work at all,
+  due to missing support for the ``-E`` option, which only got added
+  afterwards.
 
 1.5.2 (2010-10-11)
 ==================

DEVELOPERS.txt

@@ -14,4 +14,8 @@ When you're developing buildout itself, you need to know two things:
 
 - You should have specific python versions at specific locations or
   PYTHONx.x environment variables pointing to those
-  See zc.buildout testing.py, def find_python(version)
+  See zc.buildout testing.py, def find_python(version)
\ No newline at end of file
+
+  The way to start the tests for Python 2.5 for instance would be::
+
+    $ env PYTHON2.5=/path/to/python2.5 bin/test

src/zc/buildout/easy_install.py

@@ -92,7 +92,7 @@ def _has_broken_dash_S(executable):
     # file does not pass the -script.py's returncode back properly, at least in
     # some circumstances. Therefore...print statements.
     stdout, stderr = subprocess.Popen(
-        [executable, '-Sc',
+        [executable, '-S', '-c',
          'try:\n'
          '    import ConfigParser\n'
          'except ImportError:\n'