MAINT: remove useless files with outdated info from repo root and doc/.

[ci skip]

4 files changed, 0 insertions, 144 deletions

diff --git a/COMPATIBILITY b/COMPATIBILITY
deleted file mode 100644
index d2cd3cd27..000000000
--- a/COMPATIBILITY
+++ /dev/null
@@ -1,59 +0,0 @@
-
-
-X.flat returns an indexable 1-D iterator (mostly similar to an array 
-but always 1-d) --- only has .copy and .__array__  attributes of an array!!!
-
-.typecode()  -->  .dtype.char
-
-.iscontiguous() --> .flags['CONTIGUOUS'] or .flags.contiguous
-
-.byteswapped() -> .byteswap()
-
-.itemsize() -> .itemsize
-
-.toscalar() -> .item()
-
-If you used typecode characters:
-
-'c' -> 'S1' or 'c'
-'b' -> 'B'
-'1' -> 'b'
-'s' -> 'h'
-'w' -> 'H'
-'u' -> 'I'
-
-
-C -level
-
-some API calls that used to take PyObject * now take PyArrayObject * 
-(this should only cause warnings during compile and not actual problems). 
-  PyArray_Take 
-
-These commands now return a buffer that must be freed once it is used
-using PyMemData_FREE(ptr);
-
-a->descr->zero       -->   PyArray_Zero(a)
-a->descr->one        -->   PyArray_One(a)
-
-Numeric/arrayobject.h  -->  numpy/oldnumeric.h
-
-
-# These will actually work and are defines for PyArray_BYTE, 
-#   but you really should change it in your code
-PyArray_CHAR         -->  PyArray_CHAR  
-   (or PyArray_STRING which is more flexible)  
-PyArray_SBYTE        -->  PyArray_BYTE
-
-Any uses of character codes will need adjusting....
-use PyArray_XXXLTR  where XXX is the name of the type.
-
-
-If you used function pointers directly (why did you do that?),
-the arguments have changed.  Everything that was an int is now an intp.  
-Also, arrayobjects should be passed in at the end. 
-
-a->descr->cast[i](fromdata, fromstep, todata, tostep, n)
-a->descr->cast[i](fromdata, todata, n, PyArrayObject *in, PyArrayObject *out)
-   anything but single-stepping is not supported by this function
-   use the PyArray_CastXXXX functions.
-
diff --git a/DEV_README.txt b/DEV_README.txt
deleted file mode 100644
index 7dc8bceed..000000000
--- a/DEV_README.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-Thank you for your willingness to help make NumPy the best array system
-available.
-
-We have a few simple rules:
-
-   * try hard to keep the Git repository in a buildable state and to not
-     indiscriminately muck with what others have contributed.
-
-   * Simple changes (including bug fixes) and obvious improvements are
-     always welcome.  Changes that fundamentally change behavior need
-     discussion on numpy-discussions@scipy.org before anything is
-     done.
-
-   * Please add meaningful comments when you check changes in.  These
-     comments form the basis of the change-log.
-
-   * Add unit tests to exercise new code, and regression tests
-     whenever you fix a bug.
diff --git a/TEST_COMMIT b/TEST_COMMIT
deleted file mode 100644
index ca662401b..000000000
--- a/TEST_COMMIT
+++ /dev/null
@@ -1,18 +0,0 @@
-oliphant: yes
-stefanv: yes
-rkern: yes
-pearu: yes
-fperez: yes
-chanley: yes
-cookedm: yes
-swalton: yes
-eric: yes
-charris: no
-fonnesbeck: no
-afayolle: no
-dubois: no
-sasha: yes
-tim_hochberg: yes
-jarrod.millman: yes
-ariver: 2010-01-14 20:02:18
-rgommers: test build bot v3
diff --git a/doc/HOWTO_MERGE_WIKI_DOCS.rst.txt b/doc/HOWTO_MERGE_WIKI_DOCS.rst.txt
deleted file mode 100644
index 3431d28b0..000000000
--- a/doc/HOWTO_MERGE_WIKI_DOCS.rst.txt
+++ /dev/null
@@ -1,49 +0,0 @@
-========================================
-Merging documentation back from Doc-Wiki
-========================================
-
-This document describes how to merge back docstring edits from the pydocweb
-wiki (at http://docs.scipy.org/doc/) to NumPy/SciPy trunk.
-
-Basic steps
------------
-It works like this, both for NumPy and SciPy:
-
-1. Go to http://docs.scipy.org/scipy/patch/ and log in.
-2. Click on "Select OK to apply"
-3. Click on "Generate patch"
-4. Select all the text in the browser and save as a patch.
-5. Check the patch file for errors etc., edit if necessary.
-   Especially browse through the changes in example codes.
-
-   .. warning::
-
-      The examples in the documentation will be run eg. on user's computers
-      eventually, and we do a very limited screening of the edits on the wiki.
-      Hence, before committing things to SVN, you absolutely **MUST** read
-      through all changes to the examples (``>>>`` lines, ``plot::``, and
-      ``doctest::``) and check that they don't try to do anything silly and
-      dangerous.
-
-6. Apply patch (typically ``patch -p1 < newdocs.patch`` from base numpy dir).
-   This may ask you to specify location of a few files by hand, though.
-7. Run tests to see if something is broken
-8. Commit
-
-Errors in patch file
---------------------
-
-Note that it is necessary to check the generated patch before trying
-to apply.  If there are errors they are noted at the top of the
-file. There are two known reasons for errors:
-
-* If the error message is "source location for docstring is not
-  known", then the function usually needs to get handled with
-  ``add_newdoc()`` in numpy/add_newdocs.py.
-
-  This may also be a sign that the docstring is generated and assigned
-  by some automatic means, in which case the generation system may
-  need to be revised.
-
-* If there are other messages, this may indicate a bug in the
-  patch generation itself.