fixing py3 tests one by one
another small fix
revert py2-incompatible changes.  py2 is favored over py3.
tried fixing besancon for py3 compat again, and hit a dead end with this
error deep in np.ma:
>       result = self._func.__call__(a, *args, **params).view(MaskedArray)
>       E       TypeError: data type not understood
py3 'syntax error'
apparently py3 doesn't have reload in the root namespace, but both py2
and py3 have imp.reload
fixed besancon and irsa_dust.  Encoding is not even remotely fun to deal
with.
getting close... yet far... because unicode
continued work on py3
Fix minor issues highlighted by Eclipse PyDev
Python 3 compatibility fixes
a small vizier fix using str
continuing attempts to fix vizier
finally finished fixing those damned vizier test failures.  The problem
was twofold: string issues (bleh) and dictionaries being unordered
(double bleh).  OrderedDicts are so ugly, but so necessary for this
crap...
hack hack hack to hack away the py3 bugs!
astropy versions are python-version-dependent.
SIMBAD passes both py2 and py3
there is a problem with the monkeypatch scheme - it will most likely
fail for astropy v<0.3, py3.  Who cares?
py2 besancon fix
besancon works with py2 and 3 now.  I hate unicode for this.
bugfixes to sdss for py3
SHA test fixes ('rb')