v1.5.2

So this was a dumb refactoring mistake that was hidden because I was
testing on older versions not newer versions after the refactor.

It means that we were always identifying pytest as an old version, and
(seperately) the default value was then incorrect.

I will scrap the 1.5.1 release and tag this as 1.5.2

Closes: #66

When you run py.test --fixtures there's an error saying that there's no
docstring on our fixture. We can add one of those.

Damnit, this was supposed to go in before tagging the release.

Move unittest and publish into the same pipeline.

To be included in EPEL we need to support the current shipped py.test
which is 2.7. This doesn't have the 'bool' type option to addini. We
can copy this handling out of py.test until we can rely on that newer
version.

Also fixes using the @yield_fixture decorator on pytest < 3. This
wouldn't break pytest for other people, but it wouldn't have let you use
it as intended.

BZ: #1605138
Closes: #62

All the other parameters sent as part of the request are available on
the request object, except stream. Even though stream may require more
work to get setup correctly in testing we should record the parameter
value and make it available for testing.

Closes: #59

Some miscellaneous git ignores for files that tend to end up in the
repository.

When publishing to pypi we should make sure reno is installed so that we
publish release notes as part of the package.

Read the Docs moved hosting to readthedocs.io instead of
readthedocs.org. Fix single link in the project.

For additional details, see:

https://blog.readthedocs.com/securing-subdomains/

> Starting today, Read the Docs will start hosting projects from
> subdomains on the domain readthedocs.io, instead of on
> readthedocs.org. This change addresses some security concerns around
> site cookies while hosting user generated data on the same domain as
> our dashboard.

In an effort to do meaningful release notes include the details about
the repository migration in this cycle.

pytest has a different way of loading modules. We define a plugin by the
name of requests_mock that can be referenced from a pytest suite and it
will be automatically be loaded.

Closes: #28

reno was being used by openstack to generate release notes, but since
the migration we've not done anything with them. It's a great tool and
we should maintain and publish a release note that is more applicable
that tne changelog generated by PBR.

This was still trying to push to pypi. My guess is that circleci tags
aren't compared with an AND. Having both a branch and tag filter meant
it was attempting to push for anything on master branch.

Change it so that we ignore all branches for publish and only trigger on
a tag.

CircleCI just tried to push to pypi even though we didn't tag anything.
This seems to be because you have to have the entire workflow tagged
with the filters. This is stupid. Rewrite it in a way that hopefully
doesn't push to pypi all the time.

For details on the new PyPI, see the blog post:

https://pythoninsider.blogspot.ca/2018/04/new-pypi-launched-legacy-pypi-shutting.html

Try and use an automated release job to publish to pypi on tag.
Obviously I can't test this properly until we're ready to make a
release.

Cleanly separates tests from the package itself. Prevents the tests
being installed to site-packages. Tests are concerned with development,
not usage.

The tests directory was added to MANIFEST.in, so tests are still
distributed with the source distribution.

This follows the "tests outside application code" convention that is
common among many Python projects and the community.

Remove the old zuul.yaml testing configuration. Successfully moved to
circleci.

If we're going to go circle and github lets get it all set up right.

We don't want bugs on launchpad anymore. Move everything to github.

Moving to github we no longer need gerrit config files.

Build documentation using a modern version of sphinx.

Now that we can no longer rely on zuul try using circleci for testing.
Travis would be my normal go to, but there's a few things i'm not a big
fan of there.

Set literals are available on all supported Python versions (introduced
in 2.7). Prefer modern Python syntax. Additionally, set literals are
always a faster choice:

  $ python3 -m timeit 'set([1, 2, 3])'
  1000000 loops, best of 3: 0.231 usec per loop
  $ python3 -m timeit '{1, 2, 3}'
  10000000 loops, best of 3: 0.0745 usec per loop

Additionally, switch to readthedocs.io instead of readthedocs.org. Read
the Docs moved hosting to readthedocs.io instead of readthedocs.org. Fix
all links in the project. For additional details, see:

https://blog.readthedocs.com/securing-subdomains/

> Starting today, Read the Docs will start hosting projects from subdomains on
> the domain readthedocs.io, instead of on readthedocs.org. This change
> addresses some security concerns around site cookies while hosting user
> generated data on the same domain as our dashboard.

v1.4.0

This reverts commit 8f3e6577.