BF+TST: protect against odd precision changes

Windows precisions for longdouble can change at runtime; protect tests against
this.
BF: remove use of assert_allclose for old numpy

assert_allclose arrived sometime later than numpy 1.3.0; use
assert_(np.allclose ...) instead
BF: fix Windows doctest fail for "10L"

Windows apparently generated Long ints from an array shape, and so showing
"(10L,)" instead of (10,); fix by doing comparison instead of testing for
string output
Merge pull request #184 from matthew-brett/win-longdouble-fixes

BF: deal with some oddness in windows longdouble

An old installation of python x, y revealed that it's possible for windows
longdouble to change after initial import; work round this with a small hack.

Stop longdouble high integer precision check if longdouble does not have high integer precision.

Fix a windows doctest failure.