Add development/affiliated-packages.rst docs page.

At the moment this is a copy of the `package-template/README.rst` page,
but the idea is that this documentation is restructured after moving it here.
Refractor use of __init__ in io.ascii Readers

In the Readers, ther eare two ways how parameters are set.
Either they are defined in the header or data objects like this:

Method I:

class MyHeader(BaseHeader):
    comment = r'\ #'

of in the __init__ of the Reader, such as this:

Method II:
class Reader(BaseREader):
	def __init__(self):
		self.header.comment = r'\ #'

The first method makes it easy to derive from that class, the second method
makes it hard. This PR aims to transfer has much as possible from the
second method to the first. However, sometimes that's not possible
because a values are only given at runtime. Again, there is two ways for that:
1) in the __init__ such as
def __init__(self, definition='ignore', DBMS=False):

2) using the ui, such as
table.read(delimiter='%')

Back to Method I vs II:
In a class hirachy, once one class sets a value in __init__
all derived classes have to do the same, because their class attributes
will get overridden once __init__ is run.

This PR transfers a set of things from method II to I.

Does this break the API?
------------------------
If somebody derived from class in the way we used to do
(Method II was used almost exclusively) in the package: No.
If someone used Method I in class where io.ascii uses Method I: No change,
since the derived method sets the class attribute.

If someone set a class attribute, but that did not take effect because it was
overridden in one of io.ascii's __init__ methods: Yes. However, in that case
that's a bug that we fix and not an API change. If a derived class
specifically sets a value, then that value should NOT be overridden.

Is this complete?
-----------------
No, because in some cases Method I is not practical or requires the
definition or a new Data class. I think we should still do that, but I want
to run it through Travis first (tests pass locally).

Also, I have changed calls to Baseclass.__init__ -> super(Class, self).__init__
Strictly speaking this change is independent of the main goal of this PR,
but I decided to follow the astropy coding guidelines here because
(a) I had to touch all the __init__ calls anyway
(b) I have changed one or two Base classes. Using super() I don't have to
care, while I would have to be more careful with direct calls to
BaseCalss.__init__(self).

This is a partial answer to #2810
io.ascii Readers now use __init__ only to set keyword arguments
Use class attributes correctly in HTML Reader instead of __init__
Performance and stability improvements to wcs.all_world2pix - 2nd iteration

This PR is a second iteration of PR #2373 with the main difference that
now the changes are on a branch (instead of master), hopefully does not
have (yet) merge conflicts, and addresses the issue of failing doctests
from PR #2373 by using data file name relative to the package as done
in PR #2807 and with updated output of the examples.

This (and #2373) provides significant improvements to the performance
(typically 1000-2000 times faster) and stability of `wcs.all_world2pix`
function. The used algorithm is a completely vectorized implementation
of the method of consecutive approximations (fixed point iterations).
While this method is a low-order method, it is more than adequate for
geometric distortions that are typical in astrophysical images (smooth,
slowly varying polynomials).

Compared to the original implementation of `all_world2pix`, this
implementation does not require users to have SciPy installed in order
to run.

While there is a check to see if WCS contains higher-order distortions
(and return the exact solution if it does not), the method itself does
not *require* this check and will converge to the exact solution after
one iteration if WCS does not contain higher order distortions. This
check is mostly for performance purposes to avoid unnecessary iterative
solution for images that do not contain distortions (and pix->sky
requires only WCS-based, i.e., CD-only transformations).

The proposed replacement for the current implementation of
`all_world2pix` avoids unnecessary use of `wcs_world2pix` and
`all_pix2world` such as `wcs_world2pix(all_pix2world(pix))` by
replacing this with `pix2foc`. This avoids unnecessary CD-matrix based
transformation CD(CD^{-1})=I which in itself results in about 50%
performance improvement over `wcs_world2pix(all_pix2world(pix))` and
likely 25% over `all_pix2world` alone.

The function has additional code to check for *divergence* condition
(as opposite to *slow convergence*) when consecutive approximations
*diverge*. This can happen when the pixel coordinates are *far* away
from the reference pixel (distortions are "severely" extrapolated), or
for poorly-defined geometric distortions (at least for this numerical
method).

A new and improved `NoConvergence` exception has attributes that allows
users to retrieve best solution reached by the function, and indices of
*slowly converging* solutions (points) that *did not converge* in the
specified maximum number of iterations as well as indices of
*diverging* solutions (likely an indication of poorly described
distortions or very large distortions).

Finally, the new test function `test_all_world2pix_direct` (proposed as
a replacement to the old test) provides a much more improved
(versatile) and *thorough* test of the `all_world2pix` function.

These improvements address the issues raised in #1977,
https://github.com/scipy/scipy/issues/3227 that plagued
`all_world2pix`, and #2294 (in addition to performance improvements).
Fix failing doctests

Trying to fix failing doctests dues to "unexpected exception".
Change phrasing to clarify that it applies to Quantity not Unit

Closes #2375
another attempt to fix failing doctests

Changed `>>>` to `...` inside try blocks
Turning off dockets for `all_world2pix()`

I do not think it is possible to get doctests to pass with the examples
in `all_world2pix`, at least I do not know how. In addition, I do not
think this is essential: documentation builds alright, and unit tests
are OK... So, investing time in trying to fix doctests will not bring
any benefits.

The problem with doctests, I think, is that in my examples there are
print statements inside except blocks and doctests have problems when
except blocks produce anything additional to the regular traceback.
Try to fix sphinx errors after defining new classes
Skip a handful of doctests that tended to fail pseudo-nondeterministically due to involving dict keyword iteration order
Fixed a failing test of documentation build

In nitpicking mode, sphinx was producing these warnings "WARNING:
py:obj reference target not found:...". I am not sure what is the
origin of these warnings for the `all_world2pix` function but it may be
due to its interesting way of creating the docstring and "injecting" it
into the function. In any case, for each problematic object I have
changed single backquotes to double backquotes.
Don't skip the doctest.
PEP8 and formatting fixes
Fix Travis failures.
Merge pull request #2838 from mdboom/mcara-fixes

Fix #2816: Make doctest work
Cleaning up empty sections in v0.4.1 changes.  Should have been done before release but no harm.
Marking 0.4.1 released and setting up template for 0.4.2 changelog section
Merge pull request #2829 from embray/testing/skip-unreliable-doctests

Skip a handful of doctests that
Automatically recognize h5py Dataset objects in Table.read