MANIFEST.in: Distribute the tests/ directory

Avoid:

  $ python setup.py test
  ...
  warning: no files found matching '*.py' under directory 'tests'
  ...
  ----------------------------------------------------------------------
  Ran 0 tests in 0.003s

  OK

by packaging the referenced files.
Merge pull request #71 from wking/distribute-tests

MANIFEST.in: Distribute the tests/ directory
Release version 1.8.1
Use headers.get instead of indexing in test cases
Merge pull request #72 from wcdolphin/release/v1.8.1

Release version 1.8.1
Merge pull request #73 from wcdolphin/test/headers-get

Use headers.get instead of indexing in test cases
tests/base_test.py: Use __name__ for Flask's import_name

Avoid several test failures like:

  ======================================================================
  ERROR: test_credentialed_request (tests.test_credentials.AppConfigExposeHeadersTestCase)
  AppConfigExposeHeadersTestCase.test_credentialed_request
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/.../tests/base_test.py", line 82, in setUp
      self.app = Flask(self.__class__.__name__)
    File "/usr/lib64/python3.4/site-packages/flask/app.py", line 319, in __init__
      template_folder=template_folder)
    File "/usr/lib64/python3.4/site-packages/flask/helpers.py", line 741, in __init__
      self.root_path = get_root_path(self.import_name)
    File "/usr/lib64/python3.4/site-packages/flask/helpers.py", line 631, in get_root_path
      loader = pkgutil.get_loader(import_name)
    File "/usr/lib64/python3.4/pkgutil.py", line 469, in get_loader
      return find_loader(fullname)
    File "/usr/lib64/python3.4/pkgutil.py", line 490, in find_loader
      return spec.loader
  AttributeError: 'NoneType' object has no attribute 'loader'

on Python 3.4 [1].  The solution is to use an importable name [2]:

> About the First Parameter
>
> The idea of the first parameter is to give Flask an idea what
> belongs to your application. This name is used to find resources on
> the file system, can be used by extensions to improve debugging
> information and a lot more.
>
> So it’s important what you provide there. If you are using a single
> module, __name__ is always the correct value. If you however are
> using a package, it’s usually recommended to hardcode the name of
> your package there.

Previously we were using the class name (not the module name), but you
can't use that to import anything ;).

[1]: https://github.com/mitsuhiko/flask/issues/1011
[2]: http://flask.pocoo.org/docs/0.10/api/#flask.Flask
Merge pull request #74 from wking/flask-import-name

tests/base_test.py: Use __name__ for Flask's import_name
Fix improperly indented tests
Make _FLASK_CORS_EVALUATED a constant for readability
Improve handling of regular expressions for resources
Merge pull request #75 from wcdolphin/modular-tests

Small test improvements and regular expression handling
Fix bug in tests calling incorrect super classes
Merge pull request #76 from wcdolphin/patch/tests-fat-finger

Fix bug in tests calling incorrect super classes
Test options on app extesion
Improve documentation in app based example
Add support for regular expression '*' to improve API consistency
Add documentation for CORS object
Bump version to 1.9.0
Merge pull request #77 from wcdolphin/patch/options

Patch/options