RF: replace numpy.testing.assert_ with assert_true

numpy.testing.assert_ appeared in numpy 1.3.  That's pretty old, but
it's the only thing stopping us being compatible with numpy 1.2, and
nose assert_true is just as readable.
RF: no dict methods for old numpy load returns

Older numpies (at least up until 1.3) return a dict-like thing from
``np.load`` on an ``npz`` file, but without an ``items`` method or other
helpful iteration stuff.  Fall back to the ``files`` attribute on the
returned object to find the first and only array to get the design
matrix.
RF: avoid import error for numpy 1.2

measure function not present in numpy 1.2; avoid import error during
tests by deferring name lookup until benchmarks are run.  They will
still error in numpy 1.2 when benchmarking, but having the benchmarks
run is more of a luxury than having the tests run without error.
Merge pull request #252 from matthew-brett/old-numpy-compat

Old numpy compat

Make nipy compatible with numpy 1.2
RF: add py3 wrapper around csv file opening

In Python 2, csv file objects need to be binary ('rb' or 'wb' mode). In
Python 3, they need to be text, but with ``newline = ''` (see
http://docs.python.org/3/library/csv.html#csv.reader).
BF: use open4csv compatibility function

Opening files for CSV read/write differs between python 2 and python 3.
Use compatibility wrapper.
BF: manual fix for csv writing in example

Use manual fix for Python 2 / 3 differences for clarity in example.
Merge pull request #255 from matthew-brett/py3-csv-fixes

Py3 csv fixes

More detailed testing revealed a subtle error in csv file handling for Python 3 and windows. The errors are the first and second errors here:

http://nipy.bic.berkeley.edu/builders/nipy-bdist32-32/builds/4/steps/shell_4/logs/stdio

It turned out that csv files need to be opened in different modes on python 2 and 3. Make a compatibility wrapper for that and work round it in one example where that might be an issue.
BF: make windows script wrappers more robust

The script wrappers were hard-coding the python path at the time of the
creation of the binary such as an exe or an egg.  This path is likely to be
wrong after the binary is installed somewhere.  Use some minor bat file
programming to pull the Python command out of the script directly, rather like
the ``cli.exe`` trick used by setuptools.
RF: don't use setuptools to create the .exe binary

We don't need setuptools for bdist_wininst
BF: use shell=True for windows script tests

The default shell=False for windows meant that we weren't picking up
surrounding changes to the PATH, and so not finding scripts installed into a
virtualenv.
DOC: comment in windows bat, rewrite docstring

Comment to help reader of windows bat wrapper.  Point readers to
discussion of installation and bat files.
Merge pull request #257 from matthew-brett/windows-script-install

Make Windows script install more robust

We were getting errors testing the scripts on windows of form:

======================================================================
ERROR: nipy.tests.test_scripts.test_nipy_3_4d
----------------------------------------------------------------------
  ...
WindowsError: [Error 2] The system cannot find the file specified

This turned out to be because I hadn't thought out all the ways the scripts could be installed, in this case, into a virtualenv. This PR makes a more robust wrapper for the scripts, and changes the script running to pick up e.g virtualenv paths.

I documented this at http://matthew-brett.github.com/pydagogue/installing_scripts.html
BF: forgot future import for with statement

Using with statement, but forgot python 2.5 compatibility
DOC: 64 bits print 0 as 0L from vtk datasets

Work round printing difference between 32 and 64 bits for VTK datasets.
DOC: don't test uninteresting doctest

It was failing due to sympy printing, and it's not testing nipy code.
DOC: update AUTHOR and Changelog for release
DOC: update install instructions

Get us more focussed on binary installation when possible.
DOC: update README and info

* Note python 3 compatibility.
* Correct compatible versions in info.py
* Replace deprecated github downloads link with pypi
* Update ourselves to beta from alpha (high fives all round)
DOC: updating release instructions for buildbots

Making various checks and binary builds via buildbots.