[pypy-commit] pypy default: Expand a bit the explanation.

[arigo]

Author: Armin Rigo <arigo at tunes.org>
Branch: 
Changeset: r56783:f8cdc9d037ca
Date: 2012-08-21 23:41 +0200
http://bitbucket.org/pypy/pypy/changeset/f8cdc9d037ca/

Log:	Expand a bit the explanation.

diff --git a/pypy/module/_cffi_backend/test/test_c.py b/pypy/module/_cffi_backend/test/test_c.py
--- a/pypy/module/_cffi_backend/test/test_c.py
+++ b/pypy/module/_cffi_backend/test/test_c.py
@@ -1,14 +1,19 @@
 from __future__ import with_statement
 """
 This file is OBSCURE.  Really.  The purpose is to avoid copying and changing
-'test_c.py' from cffi/c/.
-Adding a test to _cffi_backend involves:
-1. add a test to cffi/_cffi_backend.c from the cffi module
-2. have it pass when you run test_c.py in cffi
-3. copy test_c.py into _backend_test.py here
-4. add the _testfunc from 1 into _test_lib.c here
-5. make the test pass in pypy
+'test_c.py' from cffi/c/ in the original CFFI repository:
+    https://bitbucket.org/cffi/cffi
 
+Adding a test here involves:
+1. add a test to cffi/c/test.py
+   - if you need a C function to call, add it into _cffi_backend.c
+     as a testfuncNN().
+2. have it pass when you run 'py.test test_c.py' in cffi
+3. check in and (if you can) push the changes
+4. copy test_c.py into _backend_test.py here, killing the few lines of header
+   - if you added a C function, it goes into _test_lib.c here
+   - if you could complete step 3, try running 'py.test test_file.py' here
+5. make the test pass in pypy ('py.test test_c.py')
 """
 import py, sys, ctypes
 if sys.version_info < (2, 6):